Linux RAID subsystem development
 help / color / mirror / Atom feed
* LILO 22.6.1-9.3 not compatible with SW RAID1 metdata >= 1.0
@ 2007-03-26 11:46 Justin Piszcz
  2007-03-29  6:33 ` Neil Brown
  0 siblings, 1 reply; 2+ messages in thread
From: Justin Piszcz @ 2007-03-26 11:46 UTC (permalink / raw)
  To: linux-raid; +Cc: johninsd

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?

Justin.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: LILO 22.6.1-9.3 not compatible with SW RAID1 metdata >= 1.0
  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
  0 siblings, 0 replies; 2+ messages in thread
From: Neil Brown @ 2007-03-29  6:33 UTC (permalink / raw)
  To: Justin Piszcz; +Cc: linux-raid, johninsd

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-03-29  6:33 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox