Bug 70141 - rc.sysinit tries to activate LVM Volume Groups twice
Summary: rc.sysinit tries to activate LVM Volume Groups twice
Keywords:
Status: CLOSED DUPLICATE of bug 78483
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 8.0
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-30 18:22 UTC by Nathan G. Grennan
Modified: 2014-03-17 02:29 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-07-30 18:44:15 UTC
Embargoed:


Attachments (Terms of Use)

Description Nathan G. Grennan 2002-07-30 18:22:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020712

Description of problem:
rc.sysinit tries to activate LVM Volume Groups twice. On my system it activates
just fine the first time and then says the volume group is already activated the
second time. I understand for that because of the different between root
partitions and other partitions this may be necessary, but for me it adds
unncessary boot messages. I recommend you either hide the output of one(doesn't
seem like a good solution, unless if selectively does it based on the success of
the first one), remove the output of both, or come out with some other more
elegant solution.

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


How reproducible:
Always

Steps to Reproduce:
1. Boot kernel with LVM support
2. Setup LVM Volume Groups
3. Reboot
	

Actual Results:  Activation of Volume Groups and then it trying to activate them
again. Then it saying they are already activated.

Expected Results:  To not see the message they are already activated.

Additional info:

Comment 1 Nathan G. Grennan 2002-07-30 18:44:10 UTC
Limbo beta2

Comment 2 Milan Kerslager 2002-11-24 11:26:08 UTC

*** This bug has been marked as a duplicate of 78483 ***


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