On Sat, Feb 28, 2009 at 03:53:31PM +0100, Stefan Richter wrote: > Martin K. Petersen wrote: > > The thing is we need to start sending RC16 to a lot of drives very soon > > because of the 4KB thing. And as we've seen RC16 breaks a lot of junk > > devices. So we need a good indicator other than the SCSI rev. because > > that unfortunately doesn't cut it. > > /Is/ the used transport protocol a good indicator for whether a > particular target breaks by READ CAPACITY 16? I have doubts. Command > set support is independent of transport protocol support. You must admit there's a striking correlation between USB devices and completely failing to follow the SCSI spec. Our current workaround of clamping USB devices at a SCSI_2 level does avoid much of the pain. I can only hope that UAS devices actually implement SCSI instead of flicking bits at random until vista doesn't crash every time you plug it in. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- 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
