From: Peter Rajnoha <prajnoha@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Alessandro MACUZ <alessandro.macuz@gmail.com>
Subject: Re: [linux-lvm] Mirrored LVM volumes and UUID
Date: Mon, 23 Sep 2013 09:39:11 +0200 [thread overview]
Message-ID: <523FF01F.4000403@redhat.com> (raw)
In-Reply-To: <CAFrGbuXqastwqEG3J5Vc7LeuiK3_SGr3GDkoaeMAJEW3FUEO+A@mail.gmail.com>
On 09/20/2013 01:30 PM, Alessandro MACUZ wrote:
> I use mirrored volumes and blkid returns the same UUID for the "raid"
> volume and the underlying volumes
>
> /dev/mapper/lvm01-root_mimage_0:
> UUID="0b88ad6f-34ed-46d6-abe3-eca0d235b353" TYPE="ext4"
> /dev/mapper/lvm01-root_mimage_1:
> UUID="0b88ad6f-34ed-46d6-abe3-eca0d235b353" TYPE="ext4"
> /dev/mapper/lvm01-root: UUID="0b88ad6f-34ed-46d6-abe3-eca0d235b353"
> TYPE="ext4"
>
> Then such ID is used in fstab to mount root based... on UUID.
>
> I wonder how fstab knows that it must use /dev/mapper/lvm01-root and not
> the others since the three of them share the same UUID, and if by
> accident the others can be erroneusly used/mounted.
When the mirror volume is activated, only top-level volumes are scanned
by blkid in udev rules (it's coordinated by 11-dm-lvm.rules and 13-dm-disk.rules
which are in /lib/udev/rules.d). In this case, it's the lvm01-root only that
is scanned by blkid within udev processing, not the *_mimage devices. Then we
end up with a symlink created only for the top-level volume in /dev/disk/by-uuid
directory. And this is what is being looked for at boot...
The similar situation happens with snapshot volumes which would end up with
same FS UUID for the origin and all its snapshots. In this case, we always give
priority to the origin volume.
Peter
next prev parent reply other threads:[~2013-09-23 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 11:30 [linux-lvm] Mirrored LVM volumes and UUID Alessandro MACUZ
2013-09-23 7:39 ` Peter Rajnoha [this message]
2013-09-25 0:24 ` Alessandro MACUZ
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=523FF01F.4000403@redhat.com \
--to=prajnoha@redhat.com \
--cc=alessandro.macuz@gmail.com \
--cc=linux-lvm@redhat.com \
/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).