Re: Does Linux support more than 2TB on a USB attached device?

On Tue, 2 Oct 2007, Richard Sharpe wrote:

> Hi,
> 
> I hope that this is not an oft repeated question, but recently during
> testing we encountered the following errors:
> 
> Oct  2 18:43:12 red-gemini mail-notification: No worthy mechs found
> Oct  2 18:45:55 red-gemini kernel: sd 7:0:0:0: [sdb] Very big device.
> Trying
> to use READ CAPACITY(16).
> Oct  2 18:45:55 red-gemini kernel: sd 7:0:0:0: [sdb] READ CAPACITY(16)
> failed
> Oct  2 18:45:55 red-gemini kernel: sd 7:0:0:0: [sdb] Result:
> hostbyte=DID_ABORT driverbyte=DRIVER_OK,SUGGEST_OK
> Oct  2 18:45:55 red-gemini kernel: sd 7:0:0:0: [sdb] Use 0xffffffff as
> device size
> Oct  2 18:45:55 red-gemini kernel: sd 7:0:0:0: [sdb] 4294967296 512-byte
> hardware sectors (2199023 MB)
> Oct  2 18:45:55 red-gemini kernel: sd 7:0:0:0: [sdb] Write Protect is
> off
> Oct  2 18:45:55 red-gemini kernel: sd 7:0:0:0: [sdb] Assuming drive
> cache:
> write through
> Oct  2 18:45:55 red-gemini kernel:  sdb:
> 
> I think we were returning 0x67FFFFFFF as the max LAB in the READ
> CAPACITY(16).
> 
> Is there something special we need to enable in Linux to allow for more
> than 2TB on a USB device?

Whether the device is USB or not should have nothing to do with it.

If you think a problem exists in the USB transfer, try turning on 
CONFIG_USB_STORAGE_DEBUG and see what the dmesg log reveals.  From the 
small amount of information above, it looks like the device didn't 
respond to the READ CAPACITY(16) command.

Alan Stern


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel