Messages in this thread | ![/](/images/icornerl.gif) | | Date | Thu, 11 Apr 2002 12:19:35 +0200 (CEST) | From | Luigi Genoni <> | Subject | Re: RAID superblock confusion |
| |
On Thu, 11 Apr 2002, Neil Brown 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 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.
Luigi
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |