From: Mitchell Laks <mlaks@verizon.net>
To: linux-raid@vger.kernel.org
Subject: hard drives with "variable" device names - mdadm raid assembly options setup
Date: Fri, 30 Dec 2005 09:08:18 -0500 [thread overview]
Message-ID: <200512300908.19390.mlaks@verizon.net> (raw)
Hi,
I notice on my system that the hard drives "device names" can change.
Ie .
The hard drives are connected to the motherboard SATA connectors or to PCI
SATA cards. They get different "names" /dev/sda or /dev/sdc depending how
many of the cards are "active".
For instance the hard drives on the motherboard itself are called /dev/sde
and /dev/sdf if there are hard drives on the 2 PCI cards and are
called /dev/sda and /dev/sdb if there are none.
This is disconcerting, as I am setting up a remote site that I want to be able
to visit rarely. I want to leave the "extra" hard drives on the PCI cards
"off" for a few months, and am worried of FUD (fear uncertainty and doubt)
when I zoom in - to adjust the system - in a few months time when I come to
connect the additional drives.
(Note: I am completely confused by udev which makes my raid life difficult -
and I completely removed it so I am working with a static /dev/
directory :) )
I notice that there is a -u option based on the fixed uuid
mdadm -A /dev/md0 -u ?????
now I read in the man page:
If precisely one device is listed, but --scan is not given, then mdadm
acts as though --scan was given and identify information is extracted
from the configuration file.
The identity can be given with the --uuid option, with the --super-
minor option, can be found in the config file, or will be taken from
the super block on the first component-device listed on the command
line.
Now I am confused: unfortunately this does not seem to help me:
if it relys on the configuration file /etc/mdadm/mdadm.conf
this config file - i create with the aid of mdadm --detail --scan
seems to still have the (problematic) "variable" device names in it.
I want only to use the uuid and not the "device name" which may change.
How can I deal effectively with my problem?
I want to set up my assemble line in my startup script so that all I need to
do is
1) connect the additional hard drives and
2) uncomment a line in a startup script that will refer to the new hard drives
only by their uuid so that I can be assured that the new device /dev/md1 will
be the new drives and not a switcheroo?
Thanks!
Mitchell
next reply other threads:[~2005-12-30 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 14:08 Mitchell Laks [this message]
2005-12-31 0:44 ` hard drives with "variable" device names - mdadm raid assembly options setup Daniel Pittman
2005-12-31 4:40 ` Max Waterman
2006-01-01 11:12 ` Daniel Pittman
2006-01-27 11:39 ` Matthias Urlichs
2005-12-31 12:01 ` Luca Berra
2005-12-31 13:09 ` Gregory Seidman
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=200512300908.19390.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.