Re: Disk Geometries reported incorrectly on 2.6.0-testX

[Andries Brouwer]

On Sun, Nov 30, 2003 at 09:27:22AM +1100, Andrew Clausen wrote:

> > > Some users, having problems, did mention the usage of 2.6 kernel. If the
> > > geometry changed during the fdisk, etc process then it could result also
> > > booting problem?
> > 
> > Let me continue to stress: geometry does not exist.
> > Consequently, it cannot change.
> 
> Let me continue to stress: geometry DOES exist.

Ha, Andrew - you know these things, I know these things - please
do not confuse matters.

My first letter had as essential content: the Linux 2.6 kernel
does not make geometry information available to user space.
Thus, if user space asks the kernel and prints an error message
in case the answer is unexpected, then such user space is broken
under 2.6. There is nothing to gain from asking the kernel.

That was a letter for you - parted should be fixed, otherwise
there will be a long sequence of users that worry that things
might be wrong.


My second letter was for Szaka and affirmed that fdisk cannot
change this non-existent geometry. You still believe in fairies,
I mean, in disk geometry, that is OK, I don't mind, but still,
whatever it is you believe in, fdisk cannot change it.


> It is an abstract construct that is stored in your BIOS that some
> configurations use and need for booting.

I am happy with that description.
"Disk geometry is: some numbers that your BIOS invents".

Of course, details are always more complicated.
What the BIOS invents may be dependent on user settings in its setup.
There are also numbers that certain operating systems or boot managers
invent. Equal to or different from what your BIOS has thought of.



> (i.e. have you got any evidence that, say, that 99.x% of Windows XP
> installations use LBA to bootstrap?)

Just ask yourself this question: does Windows XP require a bootable
partition to start below the 1024 cylinder mark?
Windows NT4 has such a restriction. Not Windows 2000 or XP.



> > Usually booting goes like this: the BIOS reads sector 0 (the MBR)
> > from the first disk, and starts the code found there. What happens
> > afterwards is up to that code. If that code uses CHS units to find
> > a partition, and if the program that wrote the table has different
> > ideas about those units than the BIOS, booting may fail.
> 
> Exactly.

Good. We agree.

Andries