> -----Original Message----- > From: Christoph Hellwig [mailto:hch@xxxxxx] > Sent: Monday, March 6, 2017 9:06 PM > To: KY Srinivasan <kys@xxxxxxxxxxxxx> > Cc: Stephen Hemminger <stephen@xxxxxxxxxxxxxxxxxx>; James > Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>; Hannes Reinecke > <hare@xxxxxxx>; Christoph Hellwig <hch@xxxxxx>; James Bottomley > <jejb@xxxxxxxxxxxxxxxxxx>; Jens Axboe <axboe@xxxxxxxxx>; Linus Torvalds > <torvalds@xxxxxxxxxxxxxxxxxxxx>; Martin K. Petersen > <martin.petersen@xxxxxxxxxx>; Dexuan Cui <decui@xxxxxxxxxxxxx>; Long > Li <longli@xxxxxxxxxxxxx>; Josh Poulson <jopoulso@xxxxxxxxxxxxx>; Adrian > Suhov (Cloudbase Solutions SRL) <v-adsuho@xxxxxxxxxxxxx>; linux- > scsi@xxxxxxxxxxxxxxx; Haiyang Zhang <haiyangz@xxxxxxxxxxxxx> > 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
