Re: [PATCH] scsi_scan: move 'INQUIRY result too short' message to debug level

2015-09-01 Thread Vitaly Kuznetsov
James Bottomley writes: > On Mon, 2015-08-31 at 14:50 +0200, Vitaly Kuznetsov wrote: >> Some Hyper-V hosts are known for ignoring SPC-2/3/4 requirement >> for 'INQUIRY data (see table ...) shall contain at least 36 bytes'. As a >> result we get tons on 'scsi 0:7:1:1: scsi scan: INQUIRY result too

Re: [PATCH] scsi_scan: move 'INQUIRY result too short' message to debug level

2015-09-01 Thread James Bottomley
On Mon, 2015-08-31 at 14:50 +0200, Vitaly Kuznetsov wrote: > Some Hyper-V hosts are known for ignoring SPC-2/3/4 requirement > for 'INQUIRY data (see table ...) shall contain at least 36 bytes'. As a > result we get tons on 'scsi 0:7:1:1: scsi scan: INQUIRY result too short > (5), using 36' message

RE: [PATCH] scsi_scan: move 'INQUIRY result too short' message to debug level

2015-08-31 Thread KY Srinivasan
[PATCH] scsi_scan: move 'INQUIRY result too short' message to > debug level > > Some Hyper-V hosts are known for ignoring SPC-2/3/4 requirement > for 'INQUIRY data (see table ...) shall contain at least 36 bytes'. As a > result we get tons on 'scsi 0:7:1:1:

[PATCH] scsi_scan: move 'INQUIRY result too short' message to debug level

2015-08-31 Thread Vitaly Kuznetsov
Some Hyper-V hosts are known for ignoring SPC-2/3/4 requirement for 'INQUIRY data (see table ...) shall contain at least 36 bytes'. As a result we get tons on 'scsi 0:7:1:1: scsi scan: INQUIRY result too short (5), using 36' messages on console. As Hyper-V is also known for its serial port being ex