Messages in this thread | | | Date | Tue, 15 Feb 2005 15:40:55 -0500 | From | Joe Krahn <> | Subject | Re: Bogus REPORT_LUNS responses breaks SCSI LUN detection |
| |
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 to force sequential >>scans. > > > There is. > Try passing scsi_mod.default_dev_flags=0x40000 > The SUSE initrd will also understand the better memorizable version > scsi_noreportlun=1. > > Devices known to be broken should be added to the blacklist with > BLIST_NOREPORTLUN. > >
Oops; I didn't see that flag. It seems it was added at the same time LUN scanning became the default. It would be good to document the availability of default_dev_flags in /Documents/scsi.
It appears that the broken RAID systems are based on Maxtronic Arrays, such as the Arena Premium 8600. They just released a fixed firmware, so the source of the problem should be fixed. (It was also broken for Mac OSX.)
Thanks, Joe Krahn - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |