Re: Bogus REPORT_LUNS responses breaks SCSI LUN detection

2005-02-18 Thread Joe Krahn
_NOREPORTLUN) I suspect that your guess of the previous command being IDENTIFY is correct. Thanks, Joe Krahn - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: Bogus REPORT_LUNS responses breaks SCSI LUN detection

2005-02-18 Thread Joe Krahn
command being IDENTIFY is correct. Thanks, Joe Krahn - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

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