[T10] Comments on 19-066r0 SPC-5 SBC-4 Add rules for multi-LUN command interlock

Kevin D Butt kdbutt at us.ibm.com
Mon Jun 10 11:32:44 PDT 2019


Gerry,

It seems to me that your proposal changes the behavior 11b of the MLU 
field such that it is not backward compatible and removes an option that 
is currently available -- and perhaps is relied on. There will no longer 
be a way to affect all logical units with a single command. Now, each and 
every logical unit must be connected and communicating before the command 
can process. This includes the SANITIZE command. Now, in a critical 
situation where a device needs sanitized in a hurry, there are additional 
requirements that might not be met before the sanitize can occur.

The entire meaning of code 10b is changed.
This command affects more than one but not all logical units contained in 
this SCSI target device. This command operates on only this logical unit 
but may impact the performance of other logical units attached to this 
SCSI target device while this command is in progress. 
The new meaning relates solely to performance, while the original has no 
specification of what the effects might be.


Also, I am not sure the replacement of "affects" with "operates on" works 
as intended. There is a subtle difference which may cause issues.
Take "This command affects operates on only this logical unit. " This 
states that the command only operates on this logical unit, but it makes 
no statement  about whether or not it might cause effects to be noticed on 
other logical units.

Aside from the obvious changes, Code 11b changes from "logical units 
contained in" to "logical units attached to ".  Now the SCSI Target device 
must become a copy manager and forward that command to other logical units 
in other SCSI Target devices to which it may be attached.

SPC-5 SBC-4 Add rules for multi-LUN command interlock
(by: Gerald Houlder)
T10/19-066r0   Uploaded: 2019/06/04   135997 bytes
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.t10.org_cgi-2Dbin_ac.pl-3Ft-3Dd-26f-3D19-2D066r0.pdf&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=9hRV7-xktvhH6SmVBcFXOfc3l09GaQd0rqZQQg8BGkY&m=blTdiXE3C3_LNPpa3A9nB0LgD3kx5-3vfdYggjQ13-c&s=bSDxB4EKrJPWWWetRGn-TVgz5hpY1Ew7wS_FQWDUrkg&e= 


Kevin D. Butt
SCSI Architect, Tape Firmware, Data Retention Infrastructure
T10 Standards
MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744
Tel: 520-799-5280
Fax: 520-799-2723 (T/L:321)
Email address: kdbutt at us.ibm.com

=========== Interesting Links ===========
[ IBM Tape Storage ]  https://www.ibm.com/it-infrastructure/storage/tape
[ SSIC - HBA/OS/Switch/Product interoperation ] 
https://www-304.ibm.com/systems/support/storage/ssic/interoperability.wss
[ LTO & 3592 ISV Support Matrix ] 
www.ibm.com/systems/resources/lto_isv_matrix.pdf
[ LTO SCSI Reference ] 
http://www-01.ibm.com/support/docview.wss?uid=ssg1S7003556
[ 3592 SCSI Reference ] 
http://www-01.ibm.com/support/docview.wss?uid=ssg1S7003248
===================================


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.t10.org/pipermail/t10/attachments/20190610/a2394f1e/attachment.html>


More information about the T10 mailing list