From: Roman Mamedov <rm@romanrm.net>
To: Reindl Harald <h.reindl@thelounge.net>
Cc: Pascal Hambourg <pascal@plouf.fr.eu.org>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: change UUID of RAID devcies
Date: Wed, 14 Sep 2022 01:28:01 +0500 [thread overview]
Message-ID: <20220914012801.5b2dce25@nvm> (raw)
In-Reply-To: <93ea4d09-d6f9-0c5f-1b8e-e610af592834@thelounge.net>
On Tue, 13 Sep 2022 21:54:21 +0200
Reindl Harald <h.reindl@thelounge.net> wrote:
> >> it's not funny when you are used to rsync your /etc/fstab over 11 years
> >> that doing so would lead in a unbootbale system on the other side
> >
> > For this I'd suggest to use LABEL=rootfs (and so on) in fstab, instead of
> > UUIDs.
> >
> > It's kind of the point of UUIDs that they are supposed to be (even globally)
> > unique, and there should not be the same UUID on two different machines
>
> that's already the case for 15 years here
>
> but there is also mdadm.conf and sadly a copy in the intird
It has never occured to me to check, but you could also specify arrays by
"name=" there, instead of UUID. See "man mdadm.conf".
And it is possible to rename arrays:
https://askubuntu.com/questions/63980/how-do-i-rename-an-mdadm-raid-array
Having same-name arrays on different hosts seems much more reasonable than
same UUIDs.
--
With respect,
Roman
next prev parent reply other threads:[~2022-09-13 20:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 15:04 change UUID of RAID devcies Reindl Harald
2022-09-12 21:37 ` Wol
2022-09-13 10:28 ` Reindl Harald
2022-09-13 10:39 ` Pascal Hambourg
2022-09-13 11:12 ` Reindl Harald
2022-09-13 11:17 ` Pascal Hambourg
2022-09-13 11:30 ` Reindl Harald
2022-09-13 11:35 ` Pascal Hambourg
2022-09-13 11:39 ` Reindl Harald
2022-09-13 11:48 ` Pascal Hambourg
2022-09-13 11:50 ` Reindl Harald
2022-09-13 12:03 ` Pascal Hambourg
2022-09-13 12:21 ` Reindl Harald
2022-09-13 12:47 ` Pascal Hambourg
2022-09-13 13:02 ` Reindl Harald
2022-09-13 14:12 ` Pascal Hambourg
2022-09-13 19:32 ` Roman Mamedov
2022-09-13 19:54 ` Reindl Harald
2022-09-13 20:28 ` Roman Mamedov [this message]
2022-09-13 20:46 ` Reindl Harald
2022-09-13 20:48 ` Roman Mamedov
2022-09-13 20:56 ` Reindl Harald
2022-09-13 21:03 ` Roman Mamedov
2022-09-13 21:11 ` Reindl Harald
2022-09-13 21:13 ` Reindl Harald
2022-09-13 17:39 ` Wols Lists
2022-09-13 18:03 ` Reindl Harald
2022-09-13 19:44 ` Wol
2022-09-13 19:53 ` Reindl Harald
2022-11-27 20:03 ` Reindl Harald
2022-09-13 15:37 ` Reindl Harald
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=20220914012801.5b2dce25@nvm \
--to=rm@romanrm.net \
--cc=h.reindl@thelounge.net \
--cc=linux-raid@vger.kernel.org \
--cc=pascal@plouf.fr.eu.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.