From: AndyLiebman@aol.com
To: linux-raid@vger.kernel.org
Subject: udev and mdadm -- I'm lost
Date: Tue, 8 Nov 2005 18:21:59 EST [thread overview]
Message-ID: <1b9.203c2461.30a28d17@aol.com> (raw)
Sorry to pose this question but a search through "man mdadm" the linux-raid
archives and google didn't really get me a very satisfactory answer.
I guess I'm accustomed to working on Linux systems with devfs. But now I had
to upgrade to a distribution with udev. I didn't notice any issues with
mdadm until today, when I was working on a server that was going to have two
separate Software RAID-0 arrays (each striping two 3ware Hardware RAID-5s).
Lo and behold, I got the "/dev/md1 doesn't exist" error when I tried to
assemble /dev/md1.
I see there is an mdadm --auto option now, but I don't feel confident I know
how to use it. Can someone tell me the correct way to create or assemble an
array with the --auto option?
I don't want to do anything fancy. I don't need partitionable RAIDS. Do I
HAVE to specify a device number?
It would just be nice to have a couple of concrete examples of the proper
syntax in "man mdadm"
If you see this, Neil, I think you do a fantastic job. I'm sorry to ask this
basic question, but just one example in the manual would be welcome. I am
using mdadm 1.9.0 and don't see one.
i.e,
mdadm -Av -a1 --uuid=xxxxx /dev/sd*
or
mdadm -Av -a /dev/md1 --uuid=xxxxx /dev/sd*
I'm not in the mood to guess...
Thanks.
Andy Liebman
next reply other threads:[~2005-11-08 23:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 23:21 AndyLiebman [this message]
2005-11-08 23:39 ` udev and mdadm -- I'm lost Sandro Dentella
2005-11-08 23:40 ` Dave Jiang
2005-11-09 7:57 ` Konstantin Olchanski
2005-11-16 17:38 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2005-11-08 23:50 AndyLiebman
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=1b9.203c2461.30a28d17@aol.com \
--to=andyliebman@aol.com \
--cc=linux-raid@vger.kernel.org \
/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.