Bug#774082: systemd: system with LVM and lvmetad does not bot after upgrade to jessie
Michael Biebl
email at michaelbiebl.de
Thu Apr 23 10:09:09 UTC 2015
Am 23.04.2015 um 11:53 schrieb Michael Biebl:
> Am 23.04.2015 um 11:40 schrieb Peter Rajnoha:
> 69-lvm-metad.rules contains that line above.
> I just tried in a VM with lvmetad enabled.
>
> A service lvm2-pvscan at 8:35.service is started, but not all LVs are
> activated. lvscan says:
>
> $ lvscan
> inactive '/dev/vg0/test1' ...
> ACTIVE '/dev/vg/big'
>
> vg0 is hosted on a /dev/md0 (mdadm RAID1).
>
>> Make sure lvm2 is compiled with "--enable-udev-systemd-background-jobs",
>> this one is used by default since lvm2 v2.02.115, but you
>> need to enable that explicitly for previous versions... Otherwise
>> there would be a rule like:
>
> I can't find this configure flag in the Debian package.
> So I assume the package was compiled without it? On the other hand, I
> have the SYSTEMD_WANTS rule you described above. So now I'm a bit confused.
I just checked the 2.02.111 source tarball. It has
UDEV_SYSTEMD_BACKGROUND_JOBS=$enableval,UDEV_SYSTEMD_BACKGROUND_JOBS=yes)
in configure.in
So, this feature is enabled by default, which explains, why I have a
lvm2-pvscan at 8:35.service instance running
But, as mentioned, one of my VGs (the one on RAID1) is not activated
when using metad.
Peter, any idea why?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20150423/5676c85f/attachment.sig>
More information about the pkg-lvm-maintainers
mailing list