From: Michal Soltys <soltys@ziu.info>
To: Doug Ledford <dledford@redhat.com>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
linux-raid@vger.kernel.org
Subject: Re: [Patch] mdadm ignoring homehost?
Date: Tue, 21 Apr 2009 10:57:49 +0200 [thread overview]
Message-ID: <49ED8A8D.3050800@ziu.info> (raw)
In-Reply-To: <B982A8CB-4054-4F17-B269-A737462B2A81@redhat.com>
Doug Ledford wrote:
> On Apr 20, 2009, at 7:47 PM, Doug Ledford wrote:
>
> Actually, I want to expand on this thought for a little bit. I'm
> obviously harping on all the symlinks and stuff that mdadm creates when
> you tell it what you want it to do. I know these were added for back
> compatibility reasons. However, the problem I have is that I work on
> mdadm for a living (well, sorta, I have 30+ other packages I also
> maintain, many of them orders of magnitude larger than mdadm, and I do
> kernel work, so my mdadm specific time is fairly small, but still it's
> paid time), and I've sat down before and tried to figure out "if I use
> name 'X' for my array, what device file gets created". The net result
> of my attempts to do that, were that I was never able to figure out just
> by running mdadm what the proper syntax for the name variable is/was.
Mdadm will create the name you want it to. If it makes sense from
kernel's perspective (aka, it's mdN or md_dN) it will be the same as you
can see under /sys - assuming it's not taken already . If not, or if
it's taken - you will have name defined in mdadm.conf under /dev or
/dev/md/, but from /sys perspective it will be something like md127 or
md_d127. If you create under /dev/md/ directory, mdadm will symlink from
/dev or not - depending on CREATE line in mdadm.conf or appropriate
commandline option.
At the same time udev will do its own stuff. It doesn't care about names
defined in mdadm.conf or specified on commandline. The stock udev
rules will create /sys -like names in /dev - including leftovers of
inactive arrays and produce all the symlinks it's told to - some from
/dev/disk/by* , some from /dev/md (which might conflict with default
mdadm's behaviour if one does mdadm -Es >>/etc/mdadm.conf and doesn't
even bother adjusting it).
By default, mdadm -Es will create devies using /dev/md/ directory with
stripped md[_] prefix (if the name is standard). In case of 1.x
superblocks, the name stored in it will be used (by default - name set
during --create w/o any md prefix).
In practice I've never used homehost, besides few tests for the sake of
this thread. The behaviour seemed consistent with the above though.
The above is under assumption of versions 2.9.x . I haven't used 3.x
branch yet.
next prev parent reply other threads:[~2009-04-21 8:57 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 16:57 mdadm ignoring homehost? Jon Nelson
2009-04-01 15:15 ` Jon Nelson
2009-04-01 22:46 ` Neil Brown
2009-04-06 14:47 ` [Patch] " Doug Ledford
2009-04-06 19:33 ` Luca Berra
2009-04-17 3:49 ` Neil Brown
2009-04-17 7:08 ` Gabor Gombas
2009-04-20 5:23 ` Neil Brown
2009-04-21 6:34 ` Gabor Gombas
2009-04-21 7:06 ` Luca Berra
2009-04-17 18:17 ` Doug Ledford
2009-04-17 18:40 ` Piergiorgio Sartor
2009-04-18 7:54 ` Luca Berra
2009-04-18 8:36 ` Piergiorgio Sartor
2009-04-18 10:19 ` Luca Berra
2009-04-18 13:06 ` Piergiorgio Sartor
2009-04-20 5:58 ` Neil Brown
2009-04-20 12:29 ` Doug Ledford
2009-04-20 18:17 ` Piergiorgio Sartor
2009-04-20 19:49 ` Leslie Rhorer
2009-04-20 20:04 ` Piergiorgio Sartor
2009-04-20 21:18 ` Luca Berra
2009-04-20 21:13 ` Luca Berra
2009-04-20 21:24 ` Piergiorgio Sartor
2009-04-20 23:47 ` Doug Ledford
2009-04-21 0:00 ` Doug Ledford
2009-04-21 8:57 ` Michal Soltys [this message]
2009-04-21 6:29 ` Luca Berra
2009-04-21 18:15 ` Piergiorgio Sartor
2009-04-22 16:06 ` Andrew Burgess
2009-04-23 1:20 ` Doug Ledford
2009-04-23 5:51 ` Luca Berra
2009-04-23 6:09 ` Luca Berra
2009-04-23 11:05 ` Doug Ledford
2009-04-23 21:31 ` Luca Berra
2009-04-24 16:46 ` Doug Ledford
2009-04-24 19:15 ` Piergiorgio Sartor
2009-04-26 11:52 ` Doug Ledford
2009-04-26 12:14 ` Piergiorgio Sartor
2009-04-26 12:58 ` Piergiorgio Sartor
2009-04-26 18:06 ` Doug Ledford
2009-04-26 19:08 ` Piergiorgio Sartor
2009-04-26 21:37 ` Michal Soltys
2009-04-18 14:34 ` Andrew Burgess
2009-04-18 8:12 ` Luca Berra
2009-04-18 8:44 ` Piergiorgio Sartor
2009-04-18 13:35 ` Doug Ledford
2009-04-18 13:52 ` Piergiorgio Sartor
2009-04-18 14:50 ` Doug Ledford
2009-04-18 14:48 ` Jon Nelson
2009-04-20 6:08 ` Neil Brown
2009-04-20 12:26 ` Luca Berra
2009-04-20 12:36 ` Doug Ledford
2009-04-18 13:58 ` Bill Davidsen
2009-04-20 7:23 ` Neil Brown
2009-04-20 13:15 ` Doug Ledford
2009-04-21 6:54 ` Neil Brown
2009-05-11 6:47 ` Neil Brown
2009-04-01 22:47 ` Michal Soltys
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=49ED8A8D.3050800@ziu.info \
--to=soltys@ziu.info \
--cc=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=piergiorgio.sartor@nexgo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.