Suggested response for LOG SENSE error

Gerry.Houlder at seagate.com Gerry.Houlder at seagate.com
Fri Jul 21 14:26:05 PDT 2006


* From the T10 Reflector (t10 at t10.org), posted by:
* Gerry.Houlder at seagate.com
*
We had a situation come up where a LOG SENSE command failed because the log
data cannot be read from its location. The actual sense data returned for
this case was clearly inappropriate, but there is not an obvious choice for
what should be reported.
My best suggestion (among things already documented in SPC) in to return
MEDIUM ERROR (3) sense key, RECORD NOT FOUND (14h, 01h) additional sense
bytes. Customers might expect that these sense bytes only apply to user
data areas, however, not reserved areas. Does anyone have a better
suggestion for this situation? Does anyone think a new ASC should be
created?
*
* 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