SMC-3 element static and volume static data

Ballard, Curtis C (StorageWorks) curtis.ballard at hp.com
Mon Aug 15 08:24:17 PDT 2011


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

Michael,
Thanks for your review and comments.
I have captured a late latter ballot comment for section 6.13.4 so we have
something in the letter ballot review document and I see Kevin has captured
your email as a T10 document number so I have referenced that in the late
letter ballot comment.	If you search for the comment it is identified as
"late 8/15/11" and will be available in R6 which we intend to post shortly
before the September face to face meeting.
The comment points out that the Volume Static Information descriptor intro
contains text saying just how static the information is but the Element
Static Information descriptor doesn't and requesting that a UA be posted if
static information is allowed to change.
We defined the element information first hen we worked on the volume
information it was clear that there were characteristics that were generally
static but technologies could allow them to change with some major
reconfiguration so that section contains an introduction pointing out that
the characteristics could change with a major event like a format.  Looking
back at the element information it looks like it would be possible for a
media changer to be implemented that would allow one of the element static
characteristics to change so I think it makes sense to have a similar
introduction there .
Curtis Ballard
Hewlett Packard
StorageWorks Division
Fort Collins, CO
(970) 898-3013
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Michael
Banther
Sent: Monday, August 15, 2011 3:06 AM
To: Kevin D Butt
Cc: t10 at t10.org
Subject: RE: SMC-3 element static and volume static data
Hi Kevin,
Thanks for getting back to me.
May I suggest that SMC-3 include a ‘shall’ clause to establish a unit
attention condition when either the element static or the volume static
information changes?  Using a unit attention to signal to the initiator that
‘static’ information has changed allows the initiator the opportunity to
cache the static information and update it only when necessary.
I apologize that I am not in a position to bring a proposal to the WG myself.
All the Best,
Michael
From: Kevin D Butt [mailto:kdbutt at us.ibm.com]
Sent: 09 August 2011 15:55
To: Michael Banther
Cc: owner-t10 at t10.org; t10 at t10.org
Subject: Re: SMC-3 element static and volume static data
Michael,
In our discussions we discussed this very item.  We resolved that "Static" is
static in the scope of not changing operationally but could change in a
configuration type event.  As an example, volume static information might
change in response to a FORMAT MEDIUM operation.
Thanks,
Kevin D. Butt
SCSI & Fibre Channel Architect, Tape Firmware
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
http://www-03.ibm.com/servers/storage/
From:	     Michael Banther
<Michael.Banther at arkivum.com>
To:	   "t10 at t10.org<mailto:t10 at t10.org>"
<t10 at t10.org<mailto:t10 at t10.org>>
Date:	     08/09/2011 06:10 AM
Subject:	SMC-3 element static and volume static data
Sent by:	owner-t10 at t10.org<mailto:owner-t10 at t10.org>
________________________________
Hi Curtis, .et.al
Is the intention of the element and volume static descriptors to be really
static, i.e. the will never change, or will their contents be static the same
way that inquiry data is static, i.e. it may change infrequently?  I’ve
looked through smc-3r15, and it looks to me like it doesn’t allow for any
change in the static data.  For instance I didn’t see any references to
establishing a unit attention condition if element or volume static data
changed.
However I can wonder if some sort of on-the-fly reconfiguration of a library
might not result in at least the element static information changing.
Just curious as, of course, I haven’t been in on the conversation in a
number of years.
All the Best,
Michael



More information about the T10 mailing list