FS#30997 - initscripts: LVM doesn't get detected after crypto assembly

Attached to Project: Arch Linux
Opened by Christian Neukirchen (chneukirchen) - Friday, 03 August 2012, 17:28 GMT
Last edited by Dave Reisner (falconindy) - Friday, 03 August 2012, 17:34 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Given an encrypted LVM volume in /etc/crypttab, after unlocking it on boot the LVM volume is not detected and thus e.g. the fsck step fails because it cannot find the device.

Running vgchange -ay manually after boot makes the LVM volumes appear and everything works.

I have USELVM="yes" in rc.conf.

Additional info:
* initscripts 2012.07.5-1

crypttab:
hdd /dev/sda2 none

fstab:
LABEL=data /data ext4 relatime 0 1

lvs upon boot:
data hdd -wi----- 280.00g


Steps to reproduce:

* Boot the machine, see fsck fail. Note that LVM detection happens before crypto opening. It should happen after again.
This task depends upon

Closed by  Dave Reisner (falconindy)
Friday, 03 August 2012, 17:34 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#30892 

Loading...