[Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs

Stefan Bader stefan.bader at canonical.com
Mon Jul 20 08:43:25 UTC 2009


Robert wrote:
> If there's so many special exceptions, then maybe the drivers need to
> be rethought in a way that is more generic.

Because there is no way to have the same driver (usb-storage) to say whether a 
device returns the total number of blocks or the highest block number (as it is 
expected). And when the drives response to actually reading the last sector in 
the case of a too high number is to return without any information and this can 
be a valid case for some other devices, you will have a hard time to come up 
with a generic solution that works for all.
Upstream already started to have a list of vendors which seem always to return 
the wrong thing. But this cannot be the default behavior as otherwise some 
devices would get a too small capacity detected.

-- 
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.




More information about the kernel-bugs mailing list