From: Neil Brown <neilb@suse.de>
To: Tim Small <tim@seoss.co.uk>
Cc: "A. Krijgsman" <a.krijgsman@draftsman.nl>, linux-raid@vger.kernel.org
Subject: Re: Debian kernel stanza after aptitude kernel upgrade
Date: Thu, 7 Oct 2010 15:16:13 +1100 [thread overview]
Message-ID: <20101007151613.05b0a873@notabene> (raw)
In-Reply-To: <4CA1CD67.4040700@seoss.co.uk>
On Tue, 28 Sep 2010 12:11:35 +0100
Tim Small <tim@seoss.co.uk> wrote:
> On 21/09/10 21:29, Neil Brown wrote:
> >> I think you need to stick the output of
> >>
> >> mdadm --examine --scan
> >>
> >> into /etc/mdadm/mdadm.conf
> >>
> > It is generally better to use
> > mdadm --detail --scan
> >
> > for generating mdadm.conf as it is more likely to get the device names
> > right. And when doing this by hand, always review the output to make sure it
> > looks right.
> >
>
>
> Thanks for that Neil - Debian (and thus Ubuntu) currently uses the
> output of "mdadm --examine --scan --config=partitions" when
> autogenerating the mdadm.conf output. Should this be considered a bug?
> If so, could you give a bit of detail, and I'll open a bug for the
> script....
>
> Thanks,
>
> Tim.
>
It all depends on what you want to do.
If you want a config file which described the current configuration, then
"--detail --scan" is definitely the thing to use.
If you want a config file that records what is on the devices currently
attached to the machine, then "--examine --scan" is what you want.
Any use of "--examine --scan" is probably better left to the auto-assembly
stuff in mdadm (mdadm -As). So Debian should probably be using --detail
--scan. However without a statement of the exactly purpose and context, one
cannot be certain.
NeilBrown
prev parent reply other threads:[~2010-10-07 4:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 10:39 Debian kernel stanza after aptitude kernel upgrade A. Krijgsman
2010-09-21 15:18 ` Tim Small
2010-09-21 15:52 ` A. Krijgsman
2010-09-21 16:06 ` Tim Small
2010-09-21 20:29 ` Neil Brown
2010-09-28 11:11 ` Tim Small
2010-10-07 4:16 ` Neil Brown [this message]
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=20101007151613.05b0a873@notabene \
--to=neilb@suse.de \
--cc=a.krijgsman@draftsman.nl \
--cc=linux-raid@vger.kernel.org \
--cc=tim@seoss.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).