Red Hat Bugzilla – Bug 156875
libata - master supports lba48 but slave does not
Last modified: 2007-11-30 17:07:17 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2
Description of problem:
Dell reports that a SATA host configured with a master supporting lba48 and a slave that does not support lba48, renders the slave inaccessible. The customer has supplied a patch that will not set the host's max_sectors when a drive supporting lba48 has been detected, since this becomes the default max sectors for any drives probed after that point.
Version-Release number of selected component (if applicable):
I patched the kernel-2.6.9-6.37.EL with the customer patch, booted kernel on i686 system with a Promise SX4 controller and a SATA ST3160023AS to verify that it was still accessible.
Created attachment 114042 [details]
Kernel bootup messages after applying linux-2.6.9-libata-lba48-max-sectors.patch
Kernel messages at boot up after applying the
RHEL4 test kernels w/ above patches available here:
Please verify that they are working and post the results here. Thanks!
fixed in CVS.
In 2.6.9-9. So its in U1.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.