From: Neil Brown <neilb@suse.de>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org, johninsd@san.rr.com
Subject: Re: LILO 22.6.1-9.3 not compatible with SW RAID1 metdata >= 1.0
Date: Thu, 29 Mar 2007 16:33:34 +1000 [thread overview]
Message-ID: <17931.23998.484806.368702@notabene.brown> (raw)
In-Reply-To: message from Justin Piszcz on Monday March 26
On Monday March 26, jpiszcz@lucidpixels.com wrote:
> Neil,
>
> Using: Debian Etch.
>
> I picked this up via http://anti.teamidiot.de/nei/2006/10/softraid_lilo/
> via google cache. Basically, LILO will not even run correctly if the
> metadata is not 0.90. After I had done that, LILO ran successfully for
> the boot md device, but I still could not boot my system until I made all of
> the root raid array volumes with 0.90 metadata.
>
> Any chance the LILO guys will fix this so it works with all forms of MD
> metadata?
I'm not sure why you address this to me. I don't have any control
over lilo. I don't even use it any more (not that grub is immensely
better in this area, just different).
I'm surprised that LILO cares about the metadata. It should just try
to map blocks on a file to blocks on the device. That obviously needs
to know something about how md works, but the metadata shouldn't be an
issue.
If the filesystem in on an md device, then check that it is raid1 and
reject if not. If it is, find the underlying devices from
GET_DISK_INFO (they might be partitions or whole devices) and possibly
add the data_offset found in sysfs is the kernel is new enough to have
that entry in sysfs. Add to that various partition mappings and you
should have a reliable mapping from file-block to device-block,
without needing to know about metadata.
NeilBrown
prev parent reply other threads:[~2007-03-29 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 11:46 LILO 22.6.1-9.3 not compatible with SW RAID1 metdata >= 1.0 Justin Piszcz
2007-03-29 6:33 ` Neil Brown [this message]
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=17931.23998.484806.368702@notabene.brown \
--to=neilb@suse.de \
--cc=johninsd@san.rr.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@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