From: Phil Turmel <philip@turmel.org>
To: Paul van der Vlis <paul@vandervlis.nl>, linux-raid@vger.kernel.org
Subject: Re: Wrong device name after hot-swap
Date: Fri, 22 Jan 2016 19:51:24 -0500 [thread overview]
Message-ID: <56A2CE8C.2090500@turmel.org> (raw)
In-Reply-To: <n7ud6o$b1f$1@ger.gmane.org>
On 01/22/2016 06:15 PM, Paul van der Vlis wrote:
> Op 22-01-16 om 23:27 schreef Phil Turmel:
>> MD stores signatures in the devices it uses that identify them for later
>> assembly. It does not depend on the device name, though it is recorded
>> in the superblock as a "last connected as" kind of indicator.
>
> So I can do it as described above?
Yes. Though I won't comment on grub part. (I've stopped using it and
am no long current.)
>> In general, you should not rely on device names in your system
>> configuration. UUIDs and filesystem labels were implemented
>> specifically to avoid this problem.
>
> So far I know I cannot configure anywhere a disk UUID or a filesytem
> label to a MD-device.
Modern udev creates /dev/disk/by-id/ and similar symlinks, but its not
important for md.
> It feels wrong when I add /dev/sdc1 to the raid, when the name is
> normally /dev/sdb1. But maybe it's no problem, because the device name
> is not impartant while booting from an MD-device.
It's not a problem. Unless you have specific member device names in
mdadm.conf. (Don't do that.)
Phil
next prev parent reply other threads:[~2016-01-23 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 21:55 Wrong device name after hot-swap Paul van der Vlis
2016-01-22 22:27 ` Phil Turmel
2016-01-22 23:15 ` Paul van der Vlis
2016-01-23 0:51 ` Phil Turmel [this message]
2016-01-23 14:45 ` Wols Lists
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=56A2CE8C.2090500@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=paul@vandervlis.nl \
/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).