From: Richard Michael <rmichael-raid@edgeofthenet.org>
To: David Greaves <david@dgreaves.com>
Cc: Richard Michael <rmichael-raid@edgeofthenet.org>,
Neil Brown <neilb@suse.de>,
LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: mdadm usage: creating arrays with helpful names?
Date: Thu, 28 Jun 2007 09:37:17 -0400 [thread overview]
Message-ID: <20070628133717.GA31927@server> (raw)
In-Reply-To: <46836D88.9010708@dgreaves.com>
On Thu, Jun 28, 2007 at 09:12:56AM +0100, David Greaves wrote:
> (back on list for google's benefit ;) and because there are some good
> questions and I don't know all the answers... )
Thanks, I didn't realize I didn't 'reply-all' to stay on the list.
> Hopefully it will snowball as people who use it then contribute back
> <hint> ;)
I will, I'm also keeping notes and changes to the man page. :)
> --auto md
Ah. Thanks for the example(s).
> >Also, when I use "--create /dev/nicename --auto=p1" (for example), I
> >also see /dev/md_d126 created. Why? There is then a /sys/block/md_d126
> >entry (presumably created by the md driver), but no /sys/block/nicename
> >entry. Why?
> Not sure who creates this, mdadm or udev
I'm guessing the kernel's md driver creates it; neither mdmadm nor udev
(just as the kernel creates, for example, sd* disk entries in /sys, but
udev creates the nice entries in /dev).
> The code isn't that hard to read and you sound like you'd follow it if
> you fancied a skim-read...
I read it for the --create option to see who created /dev/mdXX. :) I'll
take another look.
Thanks David.
Cheers.
prev parent reply other threads:[~2007-06-28 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 23:54 mdadm usage: creating arrays with helpful names? Richard Michael
2007-06-27 7:49 ` David Greaves
[not found] ` <20070627235739.GA30527@server>
2007-06-28 8:12 ` David Greaves
2007-06-28 13:37 ` Richard Michael [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=20070628133717.GA31927@server \
--to=rmichael-raid@edgeofthenet.org \
--cc=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).