[Pkg-systemd-maintainers] Bug#729272: systemd don't activate non-essential lvm over luks volumes
gustavo panizzo <gfa>
gfa at zumbi.com.ar
Wed Nov 27 20:26:23 GMT 2013
On 11/27/2013 04:03 PM, Michael Stapelberg wrote:
> control: merge -1 718190
>
> Hi gustavo,
>
> "gustavo panizzo <gfa>" <gfa at zumbi.com.ar> writes:
>> i have a compute with 2 hard disks, each is encrypted with luks
>> with different passwords and options. each luks volume belong to a
>> different VG, vg00 is where / and swap resides, is activated by
>> systemd each time the machine boots after i put the password. the other
>> luks volume is activated but no the VG
> I think this is fixed with the same fix as
> http://bugs.debian.org/718190, so I am marking it as a duplicate.
the fix suggested on #718190 does not work here :(
$ sudo lvs
LV VG Attr LSize Pool Origin Data% Move Log
Copy% Convert
lvol0 sarasa -wi------
952.00m
lvol0 vg01 -wi-a----
144.22g
nova vg01 -wi-a----
20.00g
persistente vg01 -wi-a----
14.00g
root vg01 -wi-ao---
200.00g
swap vg01 -wi-ao---
16.00g
tmp vg01 -wi-a----
4.00g
$ sudo pvs
PV VG Fmt Attr PSize PFree
/dev/mapper/dos sarasa lvm2 a-- 952.00m 0
/dev/mapper/pv vg01 lvm2 a-- 420.22g 22.00g
$ cat /etc/crypttab
# <target name> <source device> <key file> <options>
pv /dev/sda3 none luks
dos /dev/disk/by-uuid/682fe8e9-00bf-46f6-8105-773ec78cb14b
/etc/mykeyfile luks
as you can see the luks device is opened correctly and vg is discovered
but not activated :(
i'm using lvm2-2.02.98-5+systemd1 and systemd 204-5
thanks!
PS: i've tested on another machine with similar setup, i could repeat
the test on the original machine in some time
--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
More information about the Pkg-systemd-maintainers
mailing list