On 04/23/2015 12:22 PM, Michael Biebl wrote: > Am 23.04.2015 um 12:13 schrieb Michael Biebl: >> /dev/md0 has major:minor 9:0, but there is no >> lvm2-pvscan@9:0.service instance. >> >> lvm2-pvscan@8:35.service points at /dev/sdc3, which hosts /dev/vg. >> >> Why is no lvm2-pvscan@9:0.service instance triggered? Is the interaction >> between mdadm and lvm2 borked somehow? > > Looking at the udevadm info output for /dev/md0, I have > > P: /devices/virtual/block/md0 > N: md0 > S: disk/by-id/md-name-debian:0 > S: disk/by-id/md-uuid-12e60753:bdb413e0:2da3f09b:f3910a16 > S: md/0 > E: DEVLINKS=/dev/disk/by-id/md-name-debian:0 > /dev/disk/by-id/md-uuid-12e60753:bdb413e0:2da3f09b:f3910a16 /dev/md/0 > E: DEVNAME=/dev/md0 > E: DEVPATH=/devices/virtual/block/md0 > E: DEVTYPE=disk > E: MAJOR=9 > E: MD_DEVICES=2 > E: MD_DEVICE_sdc1_DEV=/dev/sdc1 > E: MD_DEVICE_sdc1_ROLE=0 > E: MD_DEVICE_sdd1_DEV=/dev/sdd1 > E: MD_DEVICE_sdd1_ROLE=1 > E: MD_DEVNAME=0 > E: MD_LEVEL=raid1 > E: MD_METADATA=1.2 > E: MD_NAME=debian:0 > E: MD_UUID=12e60753:bdb413e0:2da3f09b:f3910a16 > E: MINOR=0 > E: SUBSYSTEM=block > E: SYSTEMD_WANTS=mdmonitor.service > E: TAGS=:systemd: > E: USEC_INITIALIZED=424100 > > > I don't see a SYSTEMD_READY=1 flag there. > Where and how is that supposed to be set for /dev/md0?
I think if it's missing, it automatically means SYSTEMD_READY=1 by default (lvm rules set SYSTEMD_READY=1 just for sure). So that shouldn't be a problem here... But I don't see it being identified as LVM2 PV. It should have this line in the udev db: E: ID_FS_TYPE=LVM2_member Which is a result of blkid call. Once 69-dm-lvm-metad.rules see the LVM2_member type, it runs the pvscan on it. But it's not defined for your md0. Maybe try running udev in debug mode and check what rules are applied exactly. You don't need to reboot, just stop currently running udev: systemctl stop systemd-udevd-kernel.socket systemd-udevd-control.socket systemd-udevd.service Then run udev in debug mode: /lib/systemd/systemd-udevd --debug And then regenerated event for the md0: echo add > /sys/block/md0/uevent And check the udevd log if there's a blkid call in there and if it exports the ID_FS_TYPE=LVM2_member. -- Peter -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
