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

Gerry Houlder gerry.houlder at seagate.com
Tue Mar 1 08:20:30 PST 2022


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<https://secure-web.cisco.com/1mKoSEPWD7gQa02UIukXx2Amy1WyVqmjpgNAW1wxqf_a4btuVukXzHhH4IhphM6EQUmG5D1OxG71sa5uBvfV0UmsUT7CtEdnG-n5kw6OPwwyCHQEKVwlx2qHYUSzDkRq6mR_DXebR47o2wefMhr-wv-l2iqWhlyS2Mbc7TVgvDKF8wh7Rgd-zoCR318UaoCckfPw3B-deZ7WWMo86XO1aG2xmkfSJrVMEcAX4Dv9pj6w2b3NirEBiLFM8Uebf3plKNdzCBqOr-G1W1Y8kzFVSMj390W83cR5exLoEbYz-kuxHO8lApNz6C2OTmuJj31aVHKailLhNz-BRdnUcwpAVR5hD8M_-hOp9rAo7e6iVfWXI990JPoowlpplLQF50L523dyYP00vY8wjtKeGn3ttnwRgupLLwCLMSzL71urt1zciDzBag_53rPg0h8P7tL2V/https%3A%2F%2Fwww.t10.org%2Fcgi-bin%2Fac.pl%3Ft%3Dd%26f%3D22-032r0.pdf>



Seagate Internal


Seagate Internal


Seagate Internal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.t10.org/pipermail/t10/attachments/20220301/28e3074b/attachment.html>


More information about the T10 mailing list