From: Mike Fedyk <mfedyk@matchmail.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>,
Andreas Dilger <adilger@clusterfs.com>,
linux-kernel@vger.kernel.org, Keith Owens <kaos@ocs.com.au>
Subject: Re: RAID superblock confusion
Date: Wed, 10 Apr 2002 19:41:11 -0700 [thread overview]
Message-ID: <20020411024111.GL23513@matchmail.com> (raw)
In-Reply-To: <200204101533.g3AFXwS09100@vindaloo.ras.ucalgary.ca> <20020410184010.GC3509@turbolinux.com> <200204101924.g3AJOp113305@vindaloo.ras.ucalgary.ca> <20020410193812.GE3509@turbolinux.com> <200204102037.g3AKbmT14222@vindaloo.ras.ucalgary.ca> <15540.59659.114876.390224@notabene.cse.unsw.edu.au>
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.
Then you'd just need to make sure that if there are any block modules linked
into the kernel that raid is also linked into the kernle instead of a module.
Is there some reason why this wouldn't work (except for CML1
complications...)?
Kieth, will kbuild2.5 affect this in any way? Or is this entirely a CML2
thing?
Mike
next prev parent reply other threads:[~2002-04-11 2:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 15:33 RAID superblock confusion Richard Gooch
2002-04-10 18:40 ` Andreas Dilger
2002-04-10 19:24 ` Richard Gooch
2002-04-10 19:38 ` Andreas Dilger
2002-04-10 20:37 ` Richard Gooch
2002-04-10 21:36 ` Mike Fedyk
2002-04-10 21:39 ` Richard Gooch
2002-04-10 22:09 ` Mike Fedyk
2002-04-10 22:49 ` Richard Gooch
2002-04-10 23:36 ` Mike Fedyk
2002-04-11 10:07 ` Luigi Genoni
2002-04-13 19:29 ` Richard Gooch
2002-04-13 23:55 ` Mike Fedyk
2002-04-14 0:00 ` Richard Gooch
2002-04-14 0:17 ` Mike Fedyk
2002-04-11 1:38 ` Neil Brown
2002-04-11 2:41 ` Mike Fedyk [this message]
2002-04-11 6:42 ` Keith Owens
2002-04-11 8:37 ` Helge Hafting
2002-04-13 19:26 ` Richard Gooch
2002-04-18 1:54 ` Neil Brown
2002-04-18 2:10 ` Mike Fedyk
2002-04-18 2:23 ` Neil Brown
2002-04-18 2:59 ` Mike Fedyk
2002-04-18 14:49 ` Richard Gooch
2002-04-19 13:42 ` Luigi Genoni
2002-04-19 13:48 ` Richard Gooch
2002-04-20 0:50 ` Luigi Genoni
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 3:18 Neil Brown
2002-04-11 10:19 ` Luigi Genoni
2002-04-11 20:18 ` Mike Fedyk
2002-04-18 3:05 Neil Brown
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=20020411024111.GL23513@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=adilger@clusterfs.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=rgooch@ras.ucalgary.ca \
/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