When the mirror volume is activated, only top-level volumes are scanned
Alex
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
Many thanks Peter for your explanation,
I'll have a look at it._______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
