From: Mike Fedyk <mfedyk@matchmail.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Andreas Dilger <adilger@clusterfs.com>, linux-kernel@vger.kernel.org
Subject: Re: RAID superblock confusion
Date: Wed, 10 Apr 2002 15:09:39 -0700 [thread overview]
Message-ID: <20020410220939.GF23513@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> <20020410213645.GE23513@matchmail.com> <200204102139.g3ALd9m15133@vindaloo.ras.ucalgary.ca>
On Wed, Apr 10, 2002 at 03:39:09PM -0600, Richard Gooch wrote:
> Mike Fedyk writes:
> > On Wed, Apr 10, 2002 at 02:37:48PM -0600, Richard Gooch wrote:
> > >
> > > The device is set up (i.e. SCSI host driver is loaded) long before I
> > > do raidstart /dev/md/0
> >
> > But kernel auto-detection doesn't depend on the raidstart command. If
> > things are setup correctly, you can remove that from your init scripts.
>
> I'm not (explicitely) using auto-detection. When I insmod the raid0
> module, there are no messages about finding devices. All I get is:
> md: raid0 personality registered as nr 2
>
> Only when I run raidstart do I get kernel messages about the devices.
>
> In any case, I should be able to move my devices around (especially
> if /etc/raidtab is still correct), whether or not autostart is
> running. The behaviour I'm observing is a bug (I assume it's not a
> mis-feature, since the raidstart man page tells me that moving devices
> around should be safe).
Ehh, I ran into this a while ago. When you compile raid as modules it
doesn't use the raid superblocks for anything except for verification. I
took a quick glance at the source and the auto-detect code is ifdefed out if
you compiled as a module.
Ever since I have had raid compiled into my kernels.
Mike
next prev parent reply other threads:[~2002-04-10 22:07 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 [this message]
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
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=20020410220939.GF23513@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--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