Re: Bogus REPORT_LUNS responses breaks SCSI LUN detection

2005-02-18 Thread Joe Krahn
Andries Brouwer wrote: On Sun, Feb 13, 2005 at 11:51:00PM -0500, Kurt Garloff wrote: SuSE 9.1 Vendor: easyRAID Model: X16 Rev: 0001 Type: Direct-Access ANSI SCSI revision: 03 scsi: host 0 channel 0 id 5 lun 0x6500737952414944 has a LUN larger than currently supported. Looks like random garbage.

Re: Bogus REPORT_LUNS responses breaks SCSI LUN detection

2005-02-18 Thread Andries Brouwer
On Sun, Feb 13, 2005 at 11:51:00PM -0500, Kurt Garloff wrote: > > SuSE 9.1 > > Vendor: easyRAID Model: X16 Rev: 0001 > > Type: Direct-Access ANSI SCSI revision: 03 > > scsi: host 0 channel 0 id 5 lun 0x6500737952414944 has a LUN larger than > > currently supported. > > Looks like random

Re: Bogus REPORT_LUNS responses breaks SCSI LUN detection

2005-02-18 Thread Andries Brouwer
On Sun, Feb 13, 2005 at 11:51:00PM -0500, Kurt Garloff wrote: SuSE 9.1 Vendor: easyRAID Model: X16 Rev: 0001 Type: Direct-Access ANSI SCSI revision: 03 scsi: host 0 channel 0 id 5 lun 0x6500737952414944 has a LUN larger than currently supported. Looks like random garbage. I read e

Re: Bogus REPORT_LUNS responses breaks SCSI LUN detection

2005-02-18 Thread Joe Krahn
Andries Brouwer wrote: On Sun, Feb 13, 2005 at 11:51:00PM -0500, Kurt Garloff wrote: SuSE 9.1 Vendor: easyRAID Model: X16 Rev: 0001 Type: Direct-Access ANSI SCSI revision: 03 scsi: host 0 channel 0 id 5 lun 0x6500737952414944 has a LUN larger than currently supported. Looks like random garbage.

Re: Bogus REPORT_LUNS responses breaks SCSI LUN detection

2005-02-15 Thread Joe Krahn
Kurt Garloff wrote: On Fri, Jan 07, 2005 at 06:39:02PM -0500, Joe Krahn wrote: There are apparently several devices that return bad data for the REPORT_LUNS query, but do not return an error. The newer kernels only do sequential LUN scans if REPORT_LUNS fails. There may need to be a kernel option

Re: Bogus REPORT_LUNS responses breaks SCSI LUN detection

2005-02-15 Thread Joe Krahn
Kurt Garloff wrote: On Fri, Jan 07, 2005 at 06:39:02PM -0500, Joe Krahn wrote: There are apparently several devices that return bad data for the REPORT_LUNS query, but do not return an error. The newer kernels only do sequential LUN scans if REPORT_LUNS fails. There may need to be a kernel option

Re: Bogus REPORT_LUNS responses breaks SCSI LUN detection

2005-02-13 Thread Kurt Garloff
On Fri, Jan 07, 2005 at 06:39:02PM -0500, Joe Krahn wrote: > There are apparently several devices that return bad data > for the REPORT_LUNS query, but do not return an error. > The newer kernels only do sequential LUN scans if REPORT_LUNS > fails. There may need to be a kernel option to force

Re: Bogus REPORT_LUNS responses breaks SCSI LUN detection

2005-02-13 Thread Kurt Garloff
On Fri, Jan 07, 2005 at 06:39:02PM -0500, Joe Krahn wrote: There are apparently several devices that return bad data for the REPORT_LUNS query, but do not return an error. The newer kernels only do sequential LUN scans if REPORT_LUNS fails. There may need to be a kernel option to force