Bug 35940

Summary: fdisk has wrong limit for # of cylinders
Product: [Retired] Red Hat Linux Reporter: Marty Shannon <martys>
Component: util-linuxAssignee: Elliot Lee <sopwith>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-07-16 13:41:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Marty Shannon 2001-04-14 22:51:42 UTC
This is in SEAWOLF!

On a machine that previously had Wolverine installed (which means that it
changed the CHS info on the MBR to incorrect, but usable values), at
install time for SEAWOLF, I chose to use fdisk to correct the CHS info
(using expert mode).  I correctly set the heads to 16, the sectors to 63,
but fdisk enforces a cylinder limit of 131071 -- even though the correct
number for my drive (Maxtor 80 Gig) is 158816.  If I use fdisk to examine
the other 2 identical drives on the same box, it correctly reports their
geometry as 158816/16/63.  As long as this is the behavior, I cannot
install any Microsoft OSs on the same drive (they can't handle the 255 head
remapping, I think).  I do believe that the correct cylinder limit is 256k
- 1, not 128k - 1.

Comment 1 Elliot Lee 2001-07-18 23:40:51 UTC
I've changed the limit to 1 million. I have no clue what it's actually supposed
to be, but it's not like the current one made any more sense than the new one :)