Bug#774082: systemd: system with LVM and lvmetad does not bot after upgrade to jessie

[Michael Biebl]

Am 23.04.2015 um 12:06 schrieb Peter Rajnoha:
> 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 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).
> 
> Look if all the PVs for vg0 are present - for each PV, you should
> have lvm2-pvscan at 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 at .....service present
> for that /dev/md0.

/dev/md0 has major:minor 9:0, but there is no
lvm2-pvscan at 9:0.service instance.

lvm2-pvscan at 8:35.service points at /dev/sdc3, which hosts /dev/vg.

Why is no lvm2-pvscan at 9:0.service instance triggered? Is the interaction
between mdadm and lvm2 borked somehow?


-- 
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/515eceba/attachment.sig>