On Sun, 2009-05-03 at 17:08 +0200, Éric Piel wrote: > James Bottomley schreef: > > On Sun, 2009-05-03 at 15:57 +0200, Éric Piel wrote: > : > > > > Actually, I'd really rather not alter the default value of this setting. > > Multi-lun is rapidly becoming obsolete: any modern devices conforming to > > SCSI-3 use REPORT LUNS instead of doing LUN scanning, which gets us out > > of the issue. Conversely, the ancient devices which rely on correctly > > setting this are more likely to get upset about any change in the > > balance. > Yes, I understand. Would like me to resend the patch without the change > on the default value. IMHO, it provides a better wording. I'm not opposed in principle to the update ... however it might perhaps need to point out that modern devices (conforming to SCSI-3 and up) will ignore this setting. This also brings up (again) the problem of USB lying about the SCSI conformance level. Your changer could well have reported SCSI-3 or higher and be quite capable of doing a report lun scan, but the scsiglue.c:216 fix to the scsi compliance level pushed it back down to scsi-2 again. > > In your case, just add the changer's inquiry strings with a > > BLIST_FORCELUN. > Where, into the usb-storage driver? I guess there is no usb device which > can get confused by this, so it should work fine as well :-) It's not in the usb driver, it's in the inquiry string blacklist table in scsi_devinfo.c James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
