DS bit usage in log page 00

Kevin D Butt kdbutt at us.ibm.com
Mon Jun 22 10:32:57 PDT 2009

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

If you change this you are begging for most, if not all, of your legacy 
applications to break.	IBM will be voting for supported pages to always 
return 0.
Kevin D. Butt
SCSI & Fibre Channel Architect, Tape Firmware
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
Gerry.Houlder at seagate.com
t10 at t10.org
06/19/2009 02:25 PM
RE: DS bit usage in log page 00
* From the T10 Reflector (t10 at t10.org), posted by:
* Gerry.Houlder at seagate.com
I am posting this to SCSI reflector because it turns out that moving the 
bit from the parameter control byte to the page code byte may cause
backwards compatibility issues for some companies. The example discussed
thi these emails is the Supported Log Pages page, where the page code byte
would change from 0x00 to 0x80 if the DS bit was set for this page. 
this bit seems like the right thing to do for this page (it is described 
being undefined for LOG SELECT, so it seems not to qualify to have any
savable parameters) but software that tries to retrieve this page may be
confused by the result.
Pages that have savable parameters should not see an issue (the DS bit = 
so will look the same as before).
I ask that companies evaluate whether this item will be a problem for 
software that reads up log pages. I would like to hear opinions at the 
T10 meeting from companies on this issue.
	     "Elliott, Robert 
	     (Server Storage)" 
	     <Elliott at hp.com>						To 
	     No Phone Info	       "Gerry.Houlder at seagate.com" 
	     Available		       <Gerry.Houlder at seagate.com>, 
				       "roweber at ieee.org" 
				       <roweber at ieee.org>, Mark Evans 
	     06/19/2009 02:49	       <Mark.Evans at wdc.com> 
	     PM 							cc 
				       RE: DS bit usage in log page 00 
The history is:
1. Before SPC-3 letter ballot, log page byte 0 contained an 8-bit the PAGE
CODE field
2. In letter ballot, byte 0 bits 7:6 changed to Reserved per a Dell LB
comment that the CDBs only had 6-bit PAGE CODE fields.
3. At that time, each log parameter had its own DS bit
4. 05-242r2 (by Mark) made the parameter-specific bit DS bit obsolete and
created a new page-specific DS bit in byte 0 bit 7
The Supported Log Page page did not have conventional "log parameters" so
never had DS bits.
I think the Supported Log Pages log page (00h/00h) should always return
DS=0 to remain the same as it has always been.	The Supported Log Pages 
Subpages log page (00h/FFh) and Supported Subpages (xxh/FFh) log pages
should follow suit.
> -----Original Message-----
> From: Gerry.Houlder at seagate.com [mailto:Gerry.Houlder at seagate.com]
> Sent: Thursday, June 18, 2009 7:52 PM
> To: roweber at ieee.org; Mark Evans; Elliott, Robert (Server Storage)
> Subject: DS bit usage in log page 00
> Hi gang,
> I have noticed that log page 00 (the Supported Pages log page) has a
> statement that this log page is not defined for LOG SELECT, only for
> SENSE. Does this suggest that the DS bit for this page shall be set to
> 1?
> The definition for this bit suggests that this bit is mostly useful for
> SELECT. Should something be added to the log page 00 description
> defining
> the DS bit as set to 1 for this page?
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org

More information about the T10 mailing list