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

Robert robrwo at gmail.com
Mon Jul 20 16:48:38 UTC 2009


On 20/07/09 09:43 Stefan Bader wrote:

> 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.

These devices seem to work fine on Windows and OS/X.  What do they do 
differently?  (Especially OS/X, since it is in part open source as "Darwin".)

-- 
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