On 04/23/2015 11:53 AM, Michael Biebl wrote:
> Am 23.04.2015 um 11:40 schrieb Peter Rajnoha:
>> In systemd environment, there should also be this rule
>> which updates lvmetad for each new PV that appears in the system:
>>
>> ENV{SYSTEMD_WANTS}="lvm2-pvscan@$major:$minor.service"
>
> Debian's lvm2 package is currently at version 2.02.111.
>
> 69-lvm-metad.rules contains that line above.
> I just tried in a VM with lvmetad enabled.
OK, then proabably Debian's lvm2 is patched so the rule suitable
for system is used by default...
>
> A service lvm2-pvscan@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).
Look if all the PVs for vg0 are present - for each PV, you should
have lvm2-pvscan@major:minor.service (the last service instantiated
for the last PV making up the VG, should also activate the VG).
So lookup major:minor for your /dev/md0 and if it's the only PV making
up the vg0 just check if you have lvm2-pvscan@.....service present
for that /dev/md0.
>
>> 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.
>
>> RUN+="$env{LVM_SBIN_PATH}/lvm pvscan --background --cache --activate ay
>> --major $major --minor $minor", ENV{LVM_SCANNED}="1"
>
> I don't have this rule in 69-lvm-metad.rules
Which is OK, the ENV{SYSTEMD_WANTS} one should be used with systemd
instead. So the Debian's lvm2 is already properly configured.
--
Peter
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
