Suggested response for LOG SENSE error

Banther, Michael michael.banther at hp.com
Mon Sep 4 02:50:12 PDT 2006


Attachment #1: <A HREF="r0609040_banther_michael.vcf">banther_michael.vcf</A>

Hi Gerry,
I'd be hesitent to report a sense key of MEDIUM ERROR in this case
unless the device actually stores the log parameter on the medium.  For
removable medium devices, many end users interpret MEDIUM ERROR to mean
that they can no longer use the medium.
Whether you want to use an existing ASC/Q or propose a new one is your
choice.  I will note that SPC-4 already includes a LOG EXCEPTION ASC/Q
with the value 5B00h.
Regards,
Michael Banther
Hewlett-Packard Ltd.
+44 117 312 9503
-----Original Message-----
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of
Gerry.Houlder at seagate.com
Sent: 21 July 2006 22:26
To: t10 at t10.org
Subject: Suggested response for LOG SENSE error
* 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