[linux-lvm] lvm on top of mdraid switches from /dev/md126p2 to /dev/sdb2
osamarin68 at gmail.com
Thu May 28 08:19:47 UTC 2015
I have an imsm raid-1 device /dev/md126 assembled of /dev/sda and /dev/sdb.
I have a lvm group on top of /dev/md126p2 with some logical volumes. All
this work fine with Fedora 21.
I'm trying to fresh install Fedora 22 in some of lvm logical volume. I boot
with Fedora USB live media and run "Install to hard disk". But anaconda
does not see any existing lvm volumes so I can not choose them as a
I've created a bug https://bugzilla.redhat.com/show_bug.cgi?id=1178181 on
After some discovering I found that the reason of this issue is that
anaconda brakes lvm:
before launching anaconda pvdisplay reports there are two physical volumes
/dev/md126p2 and /dev/sdc2 (/dev/sdc is an SSD that does not belong any
raid and contains a separate lvm volume group)
after launching anaconda pvdisplay reports another two physical volumes
/dev/sdb2 and /dev/sdc2, that is wrong, because /dev/sdb is a part of
May 28 02:44:08 localhost systemd: Stopping LVM2 PV scan on device
May 28 02:44:08 localhost systemd: Stopped LVM2 PV scan on device 259:1.
May 28 02:44:08 localhost audit: <audit-1131> pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=lvm2-pvscan at 259:1 comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
May 28 02:44:09 localhost kernel: sde:
May 28 02:44:09 localhost kernel: sda: sda1 sda2
May 28 02:44:09 localhost systemd: Starting LVM2 PV scan on device 8:2...
May 28 02:44:09 localhost kernel: sdb: sdb1 sdb2
Seems lvm stopped using '/dev/md126p2'. Futhure lvm rescans force it to use
The attached storage.log contains a trace of udev events of this. All other
logs are available
What is wrong? How to force lvm to use /dev/md126p2 instead of /dev/sdb2
after starting anaconda?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the linux-lvm