Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 154394 - Duplicate devices when creating many VGs at install time
Summary: Duplicate devices when creating many VGs at install time
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: lvm
Version: 3.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Heinz Mauelshagen
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-11 13:44 UTC by Bastien Nocera
Modified: 2007-11-30 22:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-10-19 19:04:45 UTC
Target Upstream Version:

Attachments (Terms of Use)
anaconda-ks.log (deleted)
2005-04-11 13:44 UTC, Bastien Nocera
no flags Details

Description Bastien Nocera 2005-04-11 13:44:47 UTC
After an installation of RHEL3 U4 with the attached kickstart file, 3 Logical
Volumes appear with the same major/minor numbers (58:3):
brw-rw----    1 root     0         58,   1 Mar 30 21:15 /dev/VGraid04/LVraid04
brw-rw----    1 root     0         58,   2 Mar 30 21:15 /dev/VGraid05/LVraid05
brw-rw----    1 root     0         58,   3 Mar 30 21:15 /dev/VGraid06/LVraid06
brw-rw----    1 root     0         58,   3 Mar 30 21:15 /dev/VGraid07/LVraid07
brw-rw----    1 root     0         58,   0 Mar 30 21:15 /dev/VGroot/LVroot
brw-rw----    1 root     0         58,   3 Mar 30 21:15 /dev/VGroot/LVscratch
brw-rw----    1 root     0         58,   6 Mar 30 21:15 /dev/VGroot/LVswap
brw-rw----    1 root     0         58,   4 Mar 30 21:15 /dev/VGroot/LVtmp
brw-rw----    1 root     0         58,   5 Mar 30 21:15 /dev/VGroot/LVvar

Kickstart file attached below.

Comment 1 Bastien Nocera 2005-04-11 13:44:49 UTC
Created attachment 112943 [details]

Comment 2 Jeremy Katz 2005-04-12 18:03:22 UTC
Is this the installed system /dev or the installer /dev?  And the ks.cfg you
attached has all of the partitioning info commented out.

Comment 3 Bastien Nocera 2005-04-13 08:08:17 UTC
The ks.cfg is the one generated after a manual installation. I'm checking about
the /dev.

Comment 4 Bastien Nocera 2005-04-13 10:52:56 UTC
/dev is the one in the installer's root, not the one on the installed system.
Both the automated installation with the kickstart, and a manual installation
will fail.
The kickstart installation will go through but the vgscan after reboot will fail:
"/dev/VGraid06/LVraid06: The superblock could not be read or does not describe a
correct ext2 filesystem"

The manual installation will throw an error:
"An error occured trying to format VGroot/LVvar. This problem is serious and the
install cannot continue."
"mke2fs: /dev/VGroot/LVvar is mounted, will not make a filesystem here!"

Comment 5 Jeremy Katz 2005-04-13 15:33:04 UTC
The device nodes in the /dev of the installer are created by the lvm tools.

Comment 6 Heinz Mauelshagen 2005-04-14 11:18:11 UTC
Does 'vgscan ; vgmknodes' leave the same major/minor duplication behind ?

Comment 7 Thomas Uebermeier 2005-05-05 12:34:09 UTC
The customer did not try 'vgscan ; vgmknodes' as he put the system already in   
production. At the time he only tried a 'vgscan -f' which fixed the behavior. 
He looks if he can reproduce the issue on a different system, though he is not   
sure if he can get one with the same setup, therefore it is not sure, if he   
can reproduce it again.   

Comment 11 RHEL Product and Program Management 2007-10-19 19:04:45 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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