Bug 355824

Summary:	LVs within VGs with crypted PVs are not activated on boot
Product:	[openSUSE] openSUSE 10.3	Reporter:	Sebastian Hasait <clain>
Component:	Other	Assignee:	Matthias Koenig <mkoenig>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	lnussel
Version:	Final
Target Milestone:	---
Hardware:	All
OS:	openSUSE 10.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Sebastian Hasait 2008-01-23 23:48:08 UTC

Logical Volumnes within Volumne Groups which contain encrypted Physical Volumes are not activated on boot - so it is not possible to mount the LVs...

I used /etc/crypttab to decrypt my PVs and /etc/fstab to mount the LVs. The descryption key is requested during boot, but the LVs cannot be mounted.
Executing lvchange -ay VG/LV after boot and mount manually works.

I think it's because of boot.lvm is executed before boot.crypto. Maybe boot.crypto should be duplicated, so that there is boot.crypto-early (executed before boot.lvm) and boot.crypto (executed after boot.lvm), so it becomes possible to either encrypt LVs or PVs.

Thanx

Comment 1 Matthias Koenig 2008-03-12 11:04:36 UTC

Yes, I agree. This is a valid use case, which is currently not supported by our boot process, because boot.crypto runs after boot.localfs.
We really need a boot.crypto-early running before boot.lvm and boot.md.

Comment 2 Matthias Koenig 2008-04-09 15:21:54 UTC

Providing boot.crypto-early now.
Also a new option 'noearly' has been introduced to skip the device in the first invocation.

Submitted to STABLE (should be in next beta of openSUSE 11.0)