[T10] Proposal 22-032r0 [Allow inquiry data to change when capacity changes] posted to T10 site

Mark Carlson mark at carlson.net
Thu Mar 3 19:24:16 PST 2022


+1
— mark

> On Mar 3, 2022, at 8:01 PM, joe at lingua-data.com wrote:
> 
>  Agree that capacity may change, and that this shall result in unit attention. As but one example, I could have sworn that we collectively hashed this out in detail during the depop discussions.
> 
> Joe Breher
> Manager,
> lingua data, LLC
> (478) 2-Breher
> (478) 227-3437
> 
> 
> 
>> On Mar 3, 2022, at 3:19 PM, Knight, Frederick <Frederick.Knight at netapp.com> wrote:
>> 
>> The standard already allows INQUIRY data to change any time you (the device) wants.
>>  
>> If INQUIRY data changes for any reason, the device server shall establish a unit attention condition for the
>> SCSI initiator port associated with every I_T nexus (see SAM-5), with the additional sense code set to
>> INQUIRY DATA HAS CHANGED.
>>  
>> That is pretty explicit – FOR ANY REASON – which includes when capacity is changed (or even when the moon changes phase).
>>  
>>                 Fred
>>  
>>  
>> From: t10-bounces at t10.org <t10-bounces at t10.org> On Behalf Of Gerry Houlder
>> Sent: Tuesday, March 1, 2022 11:21 AM
>> To: T10 Reflector <t10 at t10.org>
>> Subject: Re: [T10] Proposal 22-032r0 [Allow inquiry data to change when capacity changes] posted to T10 site
>>  
>> NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. 
>>  
>> 
>> The purpose of the CID bit is to explicitly allows Inquiry data to change if the capacity is changed. The standard is silent on whether Inquiry data is allowed to change when capacity is changed but the behavior of products I am aware of is that Inquiry data is not changed when the capacity is changed. if CID=0 the customer gets current behavior (Inquiry data doesn't change) and if CID=1 then the Inuiry data is allowed to be changed.
>> From: Knight, Frederick <Frederick.Knight at netapp.com>
>> Sent: Monday, February 28, 2022 4:14 PM
>> To: Gerry Houlder <gerry.houlder at seagate.com>; T10 Reflector <t10 at t10.org>
>> Subject: RE: [T10] Proposal 22-032r0 [Allow inquiry data to change when capacity changes] posted to T10 site
>>  
>>  
>> This message has originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
>>  
>> Why do you need the CID bit?  The UA is already spec’ed.  If the device changes the INQUIRY data, then is already is required to send the UA.  Why do you need to tell the host that you are going to OBEY the requirements the spec already has listed.
>>  
>>                 Fred
>>  
>> From: t10-bounces at t10.org <t10-bounces at t10.org> On Behalf Of Gerry Houlder
>> Sent: Wednesday, February 23, 2022 9:29 PM
>> To: T10 Reflector <t10 at t10.org>
>> Subject: [T10] Proposal 22-032r0 [Allow inquiry data to change when capacity changes] posted to T10 site
>>  
>> NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. 
>>  
>> 
>> Proposal 22-032r0  [Allow inquiry data to change when capacity changes] is posted to T10 site. This adds a feature to SBC-5 that is similar to a feature that was approved at T13 meeting today.
>> https://www.t10.org/cgi-bin/ac.pl?t=d&f=22-032r0.pdf
>>  
>> Seagate Internal
>>  
>> Seagate Internal
>>  
>> Seagate Internal
>> _______________________________________________
>> T10 mailing list
>> T10 at t10.org
>> https://www.t10.org/mailman/listinfo/t10
> 
> _______________________________________________
> T10 mailing list
> T10 at t10.org
> https://www.t10.org/mailman/listinfo/t10
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.t10.org/pipermail/t10/attachments/20220303/915a8d7a/attachment-0001.html>


More information about the T10 mailing list