Bug 112099 - mkinitrd doesn't copy /etc/lvm/lvm.conf to initrd
Summary: mkinitrd doesn't copy /etc/lvm/lvm.conf to initrd
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: mkinitrd
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-14 17:43 UTC by Alexandre Oliva
Modified: 2007-04-18 17:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-02-13 19:19:28 UTC
Embargoed:

Attachments (Terms of Use)
Patch that arranges for /etc/lvm/lvm.conf to be copied into initrd (338 bytes, patch)
2003-12-14 17:47 UTC, Alexandre Oliva 		no flags Details | Diff
View All

Description Alexandre Oliva 2003-12-14 17:43:53 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031202

Description of problem:
When using RAID physical volumes, one has to set up /etc/lvm/lvm.conf
such that vgscan skips the component partitions of the raid devices. 
If the root filesystem is a LV of such a VG, lvm.conf must be copied
to initrd.

Version-Release number of selected component (if applicable):
mkinitrd-3.5.15.1-2

How reproducible:
Always

Steps to Reproduce:
1.Set up the root filesystem in a volume group containing raid devices
2.Try to boot kernel 2.6 with lvm2

Actual Results:  vgscan in initrd fails because of ``duplicate�� entries.

Expected Results:  Ideally, they'd be skipped automatically by lvm2,
but it doesn't take care of it by itself, relying on lvm.conf instead.
 So we have to set up lvm.conf and copy it to the initrd filesystem.

Additional info:
Comment 1 Alexandre Oliva 2003-12-14 17:47:40 UTC 
Created attachment 96523 [details]
Patch that arranges for /etc/lvm/lvm.conf to be copied into initrd
Comment 2 Jeremy Katz 2004-02-09 18:50:30 UTC 
Committed to CVS, will be in 3.5.19
Comment 3 Alexandre Oliva 2004-02-13 19:19:28 UTC 
Confirmed fixed, thanks!
Note You need to log in before you can comment on or make changes to this bug.