Bug 154394
Summary: | Duplicate devices when creating many VGs at install time | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Bastien Nocera <bnocera> | ||||
Component: | lvm | Assignee: | Heinz Mauelshagen <heinzm> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.0 | CC: | agk, dwysocha, mbroz, tao | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-10-19 19:04:45 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Bastien Nocera
2005-04-11 13:44:47 UTC
Created attachment 112943 [details]
anaconda-ks.log
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 the /dev. /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." and "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: http://www.redhat.com/security/updates/errata/ 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. |