On Tue, Oct 04, 2016 at 10:28:25AM +0200, Michal Sekletar wrote: > On Tue, Sep 27, 2016 at 5:05 PM, Lokesh Mandvekar > <l...@fedoraproject.org> wrote: > > Now, I can mount these partitions with: > > > > # lvm vgchange -ay > > > > but this still doesn't automount succesfully on a reboot. > > > > Did I miss something here? > > I'd check from emergency shell whether lvm2-pvscan@.service was run. > This instantiated systemd service is responsible for scaning LVM PVs > and auto-activating LVs on them. Note that it is spawned from udev > rules in case when certain conditions are met, e.g. block device is > identified as LVM2_member and udev event doesn't have SYSTEMD_READY=0 > property set.
Michal, thanks for the reply. What's the correct way to check if lvm2-pvscan@.service was run? I tried: # systemctl status lvm2-pvscan@.service Failed to get properties: Unit name lvm2-pvscan@.service is not valid. > > Also, there has been couple of bugfixes since systemd-222 that are > maybe related. We backported them to RHEL/CentOS 7 (systemd-219). Could you please link me to these patches if that's doable? I see the rpm source contains tons of patches. Thanks, -- Lokesh Freenode: lsm5 GPG: 0xC7C3A0DD https://keybase.io/lsm5
signature.asc
Description: PGP signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
