Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 568797

Summary:	Cannot recognize large USB or Firewire drives over 2TB
Product:	Red Hat Enterprise Linux 5	Reporter:	Daniel Senie <dts>
Component:	kernel	Assignee:	Pete Zaitcev <zaitcev>
Status:	CLOSED DUPLICATE	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.4	CC:	jwilson
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-09 07:05:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Senie 2010-02-26 16:22:16 UTC

Description of problem:

External drive, 4TB. If attached via eSATA, it is seen as 4001GB as expected. If attached via USB or Firewire, it shows as 2200GB. If attached to a Mac, it is properly seen by OS X as 4001GB via either USB or Firewire.

Version-Release number of selected component (if applicable):


How reproducible:

Simple to reproduce. Plug in drive, list with 'fdisk -l' (which doesn't like GPT partitions, but will list the details of the drives). Using eSATA, the display is as expected. Using USB or Firewire, the display shows the wrong size for the drive.


Additional info:

Appears to be a bug in the handling of drives attached via removable interfaces (USB, FW). Seen with 2.6.18-164.11.1.el5 kernel series.

Information from logs:

Feb 26 11:07:17 arugula kernel: scsi4 : SBP-2 IEEE-1394
Feb 26 11:07:17 arugula kernel: firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries)
Feb 26 11:07:17 arugula kernel:   Vendor: LaCie  2  Model: BigQuadra         Rev: 0
Feb 26 11:07:17 arugula kernel:   Type:   Direct-Access                      ANSI SCSI revision: 05
Feb 26 11:07:17 arugula kernel: sdd : very big device. try to use READ CAPACITY(16).
Feb 26 11:07:17 arugula kernel: sdd : READ CAPACITY(16) failed.Feb 26 11:07:17 arugula kernel: sdd : status=0, message=00, host=5, driver=00
Feb 26 11:07:17 arugula kernel: sdd : use 0xffffffff as device sizeFeb 26 11:07:17 arugula kernel: SCSI device sdd: 4294967296 512-byte hdwr sector
s (2199023 MB)Feb 26 11:07:17 arugula kernel: sdd: Write Protect is off
Feb 26 11:07:17 arugula kernel: sdd: cache data unavailable
Feb 26 11:07:17 arugula kernel: sdd: assuming drive cache: write through

Comment 2 Pete Zaitcev 2010-03-04 15:52:19 UTC

Please test kernel 2.6.18-183.el5.bz503864.1 from this URL:
 http://people.redhat.com/zaitcev/ftp/503864/
The test kernel only changes the USB connection, so please test USB.
If it works, I will implement as similar change in Firewire.

Comment 3 Daniel Senie 2010-03-08 17:22:22 UTC

With your test kernel, we were able to see the drive over USB at the proper size, so it appears you did solve the problem. We were able to partition the 4TB drive over USB, create an EXT3 file system on it and mount it without trouble. Please do submit this for inclusion in the distribution. We may well wind up running your test kernel on a system until the fix is included (please make sure this gets mentioned in the release notes, so we know when it's safe to switch back to normal packages).

Comment 4 Daniel Senie 2010-03-08 17:37:10 UTC

Question: to use this kernel as an interim fix, we could really use a x86_64 Xen version... any chance of that? Otherwise, what is the ETA to a kernel with the fix making it out through normal fix distribution?

Comment 5 Pete Zaitcev 2010-03-08 18:24:20 UTC

Unfortunately, scratch space is at premium, so the build was deleted.
However, I'll need to address the Firewire issue and run a build for it.
Please give me a day or so.

Comment 6 Pete Zaitcev 2010-03-09 07:05:23 UTC


*** This bug has been marked as a duplicate of bug 503864 ***