Bug 23795

Summary:	2.2 vs 2.4: drive geometry reports different logical values
Product:	[Retired] Red Hat Linux	Reporter:	Brock Organ <borgan>
Component:	kernel	Assignee:	Michael K. Johnson <johnsonm>
Status:	CLOSED RAWHIDE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1	CC:	david.balazic, rh-bugzilla
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-01-19 15:53:41 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 Brock Organ 2001-01-11 13:47:49 UTC

The /proc/ide/hd*/geometry reports different logical values for the same
drive between the 2.2 and 2.4 kernel.

[root@localhost /root]# cat /proc/ide/hda/geometry
physical     12556/16/63
logical      787/255/63
[root@localhost /root]# uname -a
Linux localhost.localdomain 2.2.16-22 #1 Tue Aug 22 15:48:40 EDT 2000 i686
unkn\own

[root@localhost /root]# cat /proc/ide/hda/geometry
physical     12556/16/63
logical      12556/16/63
[root@localhost /root]# uname -a
Linux localhost.localdomain 2.4.0-0.43.12 #1 Wed Dec 27 18:40:11 EST 2000
i686 \unknown
[root@localhost /root]#

Comment 1 Brock Organ 2001-01-11 13:50:56 UTC

a side effect of this procedure is that drives partitioned with linux in 2.2
space used the 2.2 logical numbers; but running fdisk with 2.4 will use the 2.4
logical numbers (different).  As a result, fdisk will display errors about
"partitions do not end on cylinder boundaries" ...

Comment 2 Enrico Scholz 2001-01-11 16:25:55 UTC

Another side-effect ocurred here, ist that my lilo stops with 'L' (without any
hexnumber behind).

Comment 3 Brock Organ 2001-01-19 15:53:37 UTC

verified this issue is fixed in the qa0118.1 test tree ... in my example above,
the 2.4 kernel used DOES report the same geometry as the 2.2 kernel did ...