> -----Original Message----- > From: Christoph Hellwig [mailto:[email protected]] > Sent: Monday, March 6, 2017 9:06 PM > To: KY Srinivasan <[email protected]> > Cc: Stephen Hemminger <[email protected]>; James > Bottomley <[email protected]>; Hannes Reinecke > <[email protected]>; Christoph Hellwig <[email protected]>; James Bottomley > <[email protected]>; Jens Axboe <[email protected]>; Linus Torvalds > <[email protected]>; Martin K. Petersen > <[email protected]>; Dexuan Cui <[email protected]>; Long > Li <[email protected]>; Josh Poulson <[email protected]>; Adrian > Suhov (Cloudbase Solutions SRL) <[email protected]>; linux- > [email protected]; Haiyang Zhang <[email protected]> > Subject: Re: [RFC] hv_storvsc: error handling. > > > Was the invalid LUN in the LUN0 position. Inquiry of LUN0 support (when > LUN0 is not populated) > > was added only recently to address host side issue. > > How does HyperV expect device scanning to happen for a not populated > LUN? > > REPORT SUPPORTED LUNS but nothing else on LUN 0? Maybe a TEST UNIT > READY > thrown? Or does it actually support the REPORT LUNS well known LU?
LUN0 on every target is supposed at least return enough data to support report luns scan for the target. It looks like if LUN0 on a target is empty DVD device, the INQUIRY data that is returned from the host is bogus. Stephen can give additional information on this. K. Y
