Red Hat Bugzilla – Bug 154394
Duplicate devices when creating many VGs at install time
Last modified: 2007-11-30 17:07:06 EST
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.
Created attachment 112943 [details]
Is this the installed system /dev or the installer /dev? And the ks.cfg you
attached has all of the partitioning info commented out.
The ks.cfg is the one generated after a manual installation. I'm checking about
/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
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!"
The device nodes in the /dev of the installer are created by the lvm tools.
Does 'vgscan ; vgmknodes' leave the same major/minor duplication behind ?
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.
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.