SPC-4 late letter ballot comments

Knight, Frederick Frederick.Knight at netapp.com
Wed Feb 13 17:24:05 PST 2013


Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1302130_f.htm">HTML-formatted message</a>

Comment 1:
7.8.6.9 Logical unit group designator format
A logical unit group is a group of logical units that share the same primary
target port group (see 5.16) definitions. The primary target port groups
maintain the same primary target port group asymmetric access states for all
logical units in the same logical unit group. A logical unit shall be in no
more than one logical unit group.
This paragraph is vague when it comes to the duration of the association
between the logical unit and the logical unit group.  There are two possible
options:
a)	This association is an "always" association, and it can never change;
ever.  Once a logical unit is part of a logical unit group it is never
permitted to change to a different logical unit group.
b)	The association is a "one at a time" association.  The logical unit
shall be in no more than one logical unit group at a time (i.e., there shall
be only one logical unit group designator present in page 83h).  This also
them implies that if the logical unit changes to a different logical unit
group then the value in this designator changes and the logical unit
established an INQUIRY DATA HAS CHANGED unit attention.
I believe #a is overly restrictive and not the intention.  I believe #b is
more consistent with how SCSI VPD pages operate, and as such request the
following clarification:
A logical unit group is a group of logical units that share the same primary
target port group (see 5.16) definitions. The primary target port groups
maintain the same primary target port group asymmetric access states for all
logical units in the same logical unit group. A logical unit shall be in no
more than one logical unit group.  If the logical unit group of which the
logical unit is a member changes, then the device server shall establish a
unit attention for the initiator port associated with every I_T nexus with
the additional sense code set to INQUIRY DATA HAS CHANGED.
Comment 2:
5.17.6.2 ROD types
5.17.6.2.1 ROD types overview
A copy manager uses the ROD types shown in table 110.
< ... Table 110 ... >
If a third-party copy command requests the creation of a ROD and the copy
manager does not have sufficient resources to create or maintain the ROD,
then the copy manager shall terminate the command with CHECK CONDITION
status, with the sense key set to ILLEGAL REQUEST, and the additional sense
code set to
INSUFFICIENT RESOURCES TO CREATE ROD.
Due to testing, the following change is requested:
If a third-party copy command requests the creation of a ROD and the copy
manager does not have sufficient resources to create or maintain the ROD,
then the copy manager:
a)	should terminate the command with CHECK CONDITION status, with the
sense key set to ILLEGAL REQUEST, and the additional sense code set to
INSUFFICIENT RESOURCES TO CREATE ROD; or
b)	may terminate the command with CHECK CONDITION status, with the sense
key set to ABORTED COMMAND, and the additional sense code set to INSUFFICIENT
RESOURCES.
Fred Knight



More information about the T10 mailing list