Bug 313651

Summary:	lvm2 volumge groups will not activate on boot if added after os installation
Product:	Red Hat Enterprise Linux 4	Reporter:	Shmuel Protter NDS Israel <hpuxconsulting>
Component:	lvm2	Assignee:	LVM and device-mapper development team <lvm-team>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Corey Marthaler <cmarthal>
Severity:	high	Docs Contact:
Priority:	low
Version:	4.4	CC:	agk, dwysocha, jbrassow, mbroz, prockai
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-05-14 22:55:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Shmuel Protter NDS Israel 2007-10-01 10:39:26 UTC

Description of problem: When adding a volume group to a system update 4 or
update 5 the volume group will not activate on next boot without manually adding
vgchange -a y vg01 to the /etc/rc.sysinit script


Version-Release number of selected component (if applicable):
lvm2 update 4 and update 5


How reproducible:
100%

Steps to Reproduce:
1. Setup system with all but /boot lvm
2. pvcreate a new disk after partitioning with fdisk
3. vgcreate a volume group (example vg01)
4. lvcreate a logical volume
5. mkfs.ext3 (filesystems does not matter)
6. create a mountpoint mkdir /lvol1
7. modify /etc/fstab to include /dev/vg01/lvol1 /lvol1 ext3 mount
8. boot system

  
Actual results:

System should mount the file system, it actually boots into debug mode and the
path /dev/vg01 does not exist. If you manually run vgchange -a y vg01 the path
is created and visible.

Same results when logical volume/vg group creates sys system-config-lvm

A work around is as follows:

Add this to /etc/rc.sysinit

/sbin/vgchange -a y vg01
/sbin/mount -t ext3 /dev/vg01/lvol1 /lvol1

Filesystem choosen does not matter. Not using lvm2 avoids the problem.

I have replicated this behavior on RH 4 update 4 and update 5.
Expected results:


Additional info:

Comment 1 Jonathan Earl Brassow 2008-10-22 00:26:15 UTC

Perhaps it's a little late to be asking about this one...  So, the first question  should be, are you still having this issue?

We would need to see /etc/fstab, /etc/lvm/lvm.conf, and 'vgs; lvs' output.

Comment 2 Milan Broz 2010-05-14 22:55:38 UTC

In needinfo for more than two years, closing.