protection questions

Gary.Franco at Emulex.Com Gary.Franco at Emulex.Com
Mon Dec 4 10:08:43 PST 2006


Formatted message: <A HREF="r0612042_f.htm">HTML-formatted message</A>

Since the following is described in SBC3r07 I have a couple stupid
questions
4.17.2.3 Type 1 protection
a) defines the content of the LOGICAL BLOCK GUARD field;
b) does not define the content of the LOGICAL BLOCK APPLICATION TAG
field; and
c) defines the content the LOGICAL BLOCK REFERENCE TAG field.
4.17.2.4 Type 2 protection
a) defines the content of the LOGICAL BLOCK GUARD field;
b) does not define the content of the LOGICAL BLOCK APPLICATION TAG
field; and
c) defines, except for the first logical block addressed by the command,
the content of the LOGICAL BLOCK REFERENCE TAG field.
4.17.2.5 Type 3 protection
a) defines the content of the LOGICAL BLOCK GUARD field within the
logical blocks of the data-in buffer and/or data-out buffer;
b) does not define the content of the LOGICAL BLOCK APPLICATION TAG
field; and
c) does not define the content of the LOGICAL BLOCK REFERENCE TAG field.
My confusion is as follows:
1)	when the protection word says to check the LOGICAL BLOCK
APPLICATION TAG, is that imply that it is only checked for Type 2
protection when the 32-byte CDBs are used? And for Type 1 / Type 3
protection it should be ignored altogether even though the WRPROTECT,
etc. says to check it.
2)	Does this logic hold as well when the protection type specifies
that these fields are not defined?
3)	Or only when Type 2 protection is defined and the APPLICATION
TAG OWNERSHIP is set to one?
This information changes the BlockGuard profile definitions somewhat.
Please respond ASAP,
Thanks in advance.
__________________________________
Gary Franco Consultant Engineer 
Emulex Network Systems 
972-671-7433 Dallas Office
972-671-7435 Dallas Office Fax 
720-652-6387 Longmont Colorado Office 
720-494-1817 Longmont Colorado Office Fax
972-839-5694 Cell Phone
Today's Quote 
The mind is like a parachute. It doesn't work unless it's open.
-Unknown



More information about the T10 mailing list