Re: RAID superblock confusion

[Mike Fedyk <mfedyk@matchmail.com>]

On Thu, Apr 11, 2002 at 12:19:35PM +0200, Luigi Genoni wrote:
> > On Wednesday April 10, mfedyk@matchmail.com wrote:
> > > On Thu, Apr 11, 2002 at 11:38:19AM +1000, Neil Brown wrote:
> > > > autodetect is the other alternative.  However, as has been mentioned,
> > > > it does not and cannot work with md as a module.  This is because
> > > > devices can only be register for autodetection after md.o is loaded,
> > > > and autodetection is done at the time that md is loaded.  So
> > > > autodetection can only work if the device driver and md are loaded at
> > > > simultaneously.  i.e. they are compiled into the kernel.
> > >
> > > Ahh, but if you use initrd you can even have the ide and scsi drivers as
> > > modules.
> > >
> > > What is needed is to make the disk modules depend on the raid modules (only
> > > if the raid code is enabled of course) so that modprobe can load the raid
> > > modules first.
> you are supposing that I load md modules and raid module together, mostly

md and raid is the same and not split yet as Niel proposed.

> during boot with initrd. In the reality I have some servers with more that
> 200 days of uptime, and I have to change external disks sometime. I do
> usually have two external boxes, and something like 8/20 disks (two scsi
> controllers),  and different raid on different disks. You see, it is not
> that easy.

Currently, if you have raid compiled as modules the autodetection does not
work, and is disabled.  The issue here is enabling autodetection from the
modules, wheather that be at boot time or not.  If you use raid modules you
won't get the autodetection and the features that come with that.

When adding a new disk, you would have to add it to an array manually with
the raidtools2 anyway, so this is unchanged.

Mike