From: Mitchell Laks <mlaks@verizon.net>
To: linux-raid@vger.kernel.org
Subject: /dev/.static/dev/md0 works - weird...
Date: Sun, 26 Jun 2005 16:21:01 -0400 [thread overview]
Message-ID: <200506261621.01799.mlaks@verizon.net> (raw)
Now I try the following.
I notice that on this sysem (which has that damn udev installed)
/dev/md0 disappears on reboot.
So I see why mdadm --detail --scan came up with that weird
/dev/.static/dev/md0,
/dev/.static/dev/md0 at least this device persists after reboot:
that seems to stay around after reboot...
So I edit /etc/mdadm/mdadm.conf to read as follows
Device /dev/.static/dev/hdg1 /dev/.static/dev/hdb1
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=86af4f07:91fe306c:d1cb5c86:e87dc7de
devices=/dev/.static/dev/hdg1
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=19def19e:3995fe1e:5470d62a:c44b069c
devices=/dev/.static/dev/hdb1
and now I reboot the system.
And now if I run
mdadm -A --run /dev/.static/dev/md0 /dev/hdb1
it starts it running. and i can mount it.
mount -t ext3 /dev/.static/dev/md0 /big1
So I think that I must create a init.d script to run at the end of the boot to
do
mdadm -A --run /dev/.static/dev/md0 /dev/hdb1
mount -t ext3 /dev/.static/dev/md0 /big1
and then I won't have problems....
However I think that raids should boot as long as they are intact, as a matter
of policy. Otherwise we lose our ability to rely upon them for remote
servers...
Mitchell Laks
next reply other threads:[~2005-06-26 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 20:21 Mitchell Laks [this message]
2005-07-07 6:18 ` RAID1 assembly requires manual "mdadm --run" Molle Bestefich
2005-07-08 11:42 ` Neil Brown
2005-07-08 18:38 ` Molle Bestefich
2005-07-08 23:12 ` Tyler
2005-07-10 9:10 ` Molle Bestefich
2005-07-09 1:44 ` Neil Brown
2005-07-10 9:45 ` Molle Bestefich
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=200506261621.01799.mlaks@verizon.net \
--to=mlaks@verizon.net \
--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.