From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Kris Karas <ktk@bigfoot.com>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: 2.6 Partitioning bug with LILO
Date: Sat, 13 Jan 2007 21:58:38 +0100 [thread overview]
Message-ID: <20070113205838.GA2875@apps.cwi.nl> (raw)
In-Reply-To: <45A81728.6060405@bigfoot.com>
On Fri, Jan 12, 2007 at 06:18:00PM -0500, Kris Karas wrote:
> Hello Andries,
>
> I noticed you're listed as the maintainer for the disk
> geometry/partitioning logic in the 2.6 kernel, so I'm sending this to
> you, as I think this bug is most likely in that part of the code, ...
>
> I've been bug-hunting with John Coffman to solve an issue where running
> LILO trashes the ext2 metadata on my /boot partition. The consensus so
> far is that it's not LILO at all, but rather some subtle bug in the
> kernel that's the culprit. I can reproduce it easily enough on 2.6, but
> not on 2.4, which further suggests its kernel-related.
>
> If one does:
>
> umount /boot
> e2fsck -f -y /dev/hda1
> mount /dev/hda1 /boot
> lilo
> umount /boot
> e2fsck -f -y /dev/hda1
>
> the second run of e2fsck will report fixable block bitmap errors.
It is easy to see the cause of this.
There is an old problem with the Linux whole disk device /dev/hda
namely that there is aliasing with /dev/hdaN.
I don't know whether there exist kernels that fix this problem -
as far as I know this has been a problem since ancient times.
But, given the fact that this is a well-known problem of the kernel,
a utility should be careful to avoid problems and flush buffers
at appropriate times.
Now that lilo is one of the few utilities to write to /dev/hda,
it should be fixed.
[And yes, also the kernel should be fixed.]
Andries
[let me cc linux-kernel]
parent reply other threads:[~2007-01-13 20:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <45A81728.6060405@bigfoot.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070113205838.GA2875@apps.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=ktk@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox