Obsoleting Log Page Thresholding work (14-249)

Ralph Weber Ralph.Weber at wdc.com
Thu Nov 13 08:52:36 PST 2014

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

Let me see! I have a major competitor who challenges WD engineers to do our
best work every day and an extremely valuable WD customer both of whom are
saying the same thing.
I don't even have to call in my team of crack rocket scientists to determine
the status of the posted 14-249r1.
Thanks for your support,
From: owner-t10 at t10.org [owner-t10 at t10.org] on behalf of Ballard, Curtis C
(HP Storage) [curtis.ballard at hp.com]
Sent: Thursday, November 13, 2014 9:56 AM
To: Kevin D Butt; T10 Reflector (t10 at t10.org)
Subject: RE: Obsoleting Log Page Thresholding work (14-249)
I don’t think that makes any sense at all.  As a vendor of products that
supports those bits as defined in SPC-4 HP feels that either the bits need to
be left as is or marked as obsolete.  Obsolete allows us to continue to use
the SPC-4 definition.  Redefining as vendor specific would remove all meaning
and make it impossible to recover those bits at any time in the future.
It feels incomplete but it might be possible to have an approach where the
ability to report THRESHOLD CONDITION MET it still defined as a result of a
threshold comparison but remove the device server control using ETC and TMC
I think that would mean the bits are made obsolete but it would leave the
Page Control field in the log parameter control byte definitions for
“Threshold values” and “Default threshold values” intact then create a new
clause somewhere (probably a model clause) that describes threshold criteria
checking/reporting with the method for specifying whether threshold checking
is performed and specifying threshold met criteria as ‘outside the scope of
the standards’.
Curtis Ballard
Hewlett-Packard Company
+1 970 898 3013 / Tel
Curtis.Ballard at hp.com / Email
Fort Collins, CO
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Kevin D Butt
Sent: Wednesday, November 12, 2014 2:51 PM
To: T10 Reflector (t10 at t10.org)
Subject: Obsoleting Log Page Thresholding work (14-249)
During last weeks CAP, Ralph presented a proposal to obsolete thresholding
(14-249r1).  IBM supported removing the ETC bit and the TMC field but did not
support removing the Threshold values and the Default threshold values from
the Page control (PC) field.  I was given the task of coming back with a
proposal for how to accomplish the obsoletion of ETC and TMC but still keep
the threshold values in the page control field.
After discussing this with my engineers, we would like to keep Ralph's good
work with the exception of instead of obsoleting the Threshold values and the
Default threshold values from the Page control (PC) field they instead be
made vendor-specific.  This solves the problem of backward compatibility to
anybody who might have used them as specified in SPC-4 and still allows our
use of them.
Does anybody object to this course of action?
Kevin D. Butt
SCSI Architect, Tape Firmware, T10 Standards
Data Protection & Retention
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

More information about the T10 mailing list