Bug 149514 - LVM2 and LVM only get re-initialized if /etc/raidtab exists
Summary: LVM2 and LVM only get re-initialized if /etc/raidtab exists
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts   
(Show other bugs)
Version: 3
Hardware: All Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
: 158949 165877 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2005-02-23 18:36 UTC by Murray Schwalbaum
Modified: 2014-03-17 02:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-02-25 17:09:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Murray Schwalbaum 2005-02-23 18:36:07 UTC
Description of problem:

If you have a /dev/md* devices setup as a physical volume and do not use
/etc/raidtab (you use only mdadm.conf), the sections to do the vgcans do not
run. They are enclosed in an if statement of  [ -f /etc/raidtab ].

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

How reproducible:
See steps below.

Steps to Reproduce:
Install FC3.
Create /dev/md0.
Create a physical volume on /dev/md0.
Create a volume group called vol00 including /dev/md0.
Create a logical volume called lvol0 with vol00.

Actual results:
It should not initialize until you touch /etc/raidtab.

Expected results:
The lvm should be setup properly.

Additional info:

Look at /etc/rc.sysinit. The code comented with 
"# LVM2 initialization, take 2" only gets run if /etc/raidtab exists. This file
is not created if you create md devices with anaconda.


Move the "take 2" initialization out of the -f /etc/raidtab statement.

Comment 1 Bill Nottingham 2005-02-23 18:54:49 UTC
What release are you looking at - you filed this against 'test3'.

Comment 2 Murray Schwalbaum 2005-02-25 02:23:14 UTC
Sorry. Core 3. I'll check to see if it exists on RHEL/CentOS 4.

Comment 3 Murray Schwalbaum 2005-02-25 13:35:30 UTC
It exists on RHEL/CentOS 4 (supprise supprise). I haven't tested it, because it
would mean reinstalling the system to get an older kernel and mean downtime for
the system.

If you verify that what I am experiencing is a bug, I can put in an RHEL 4
ticket (if you think that would get it solved faster).

Comment 4 Bill Nottingham 2005-02-25 17:09:29 UTC
Fixed on the RHEL4 & FC3 branches. Note that when it gets pushed as an
update for either probably depends on what other bugs are found.

This code isn't in the current devel tree, so the problem is already
fixed there. Closing as fixed in rawhide.

Comment 5 Bill Nottingham 2005-05-27 02:41:58 UTC
*** Bug 158949 has been marked as a duplicate of this bug. ***

Comment 6 Bill Nottingham 2005-08-19 06:57:41 UTC
*** Bug 165877 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.