SPC-4 section 5.6 - late letter ballot comment.

Ralph Weber Ralph.Weber at wdc.com
Thu Mar 6 13:40:27 PST 2014


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

As I was told many moons ago upon arrival for my first big-time programming
job in New England, "He who proposes, disposes."
If you do not like the current example, don't whine about it. Propose a
better one.
Otherwise ... It is only an example, and your mileage may vary.
All the best,
.Ralph
________________________________
From: owner-t10 at t10.org [owner-t10 at t10.org] on behalf of Gerry Houlder
[gerry.houlder at seagate.com]
Sent: Thursday, March 06, 2014 1:35 PM
To: T10 Reflector
Subject: Re: SPC-4 section 5.6 - late letter ballot comment.
I presume the peripheral device is required to keep the information
non-volatile. If the host system does something (like reformat the medium)
that should cause the identifying information to change, then the host system
is expected to send a new SET IDENTIFYING INFORMATION command to cause the
change. The host system may well want to continue using the same device with
the same volume label after the reformatting, but the peripheral device can't
know what the host system desires.
There certainly is no rule that certain events cause the identifying
information to return to some default pattern.
On Thu, Mar 6, 2014 at 12:59 PM, Black, David
<david.black at emc.com> wrote:
* From the T10 Reflector (t10 at t10.org<mailto:t10 at t10.org>), posted by:
* "Black, David" <david.black at emc.com>
*
The second and third paragraphs say:
	Identifying information shall persist through power cycles (i.e., be
stored
	in non-volatile storage), hard resets, logical unit resets, I_T nexus
losses,
	media format operations, and media replacement.
	Table 61 defines the identifying information types.
The first Identifying Information Type entry in that table says:
	Peripheral device identifying information: a value describing
	the peripheral device (e.g., an operating system volume label)
The example is a problem.  Volume labels generally do not survive media
format
operations and media replacement.
Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953	      FAX: +1 (508) 293-7786
david.black at emc.com        Mobile: +1 (978)
394-7754
----------------------------------------------------
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to
majordomo at t10.org<mailto:majordomo at t10.org>



More information about the T10 mailing list