Red Hat Bugzilla – Full Text Bug Listing
|Summary:||anaconda created a new filesystem with the same label as existing|
|Product:||[Fedora] Fedora||Reporter:||Charles R. Anderson <cra>|
|Component:||anaconda||Assignee:||Anaconda Maintenance Team <anaconda-maint-list>|
|Status:||CLOSED RAWHIDE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2008-04-01 16:41:23 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Charles R. Anderson 2008-01-22 18:31:56 EST
Description of problem: I have a dual-boot system running F7 on one VolumeGroup and rawhide on another, with two separate /boot partitions. Anaconda labeled /dev/sda3 as /boot even though /dev/sda2 already has this label from my F7 install. Version-Release number of selected component (if applicable): 184.108.40.206-1 How reproducible: didn't try Steps to Reproduce: 1. Install F7 2. Install rawhide-20080121 with a new /boot partition 3. Check labels of F7 vs. F9 /boot partitions Actual results: From rescue CD: sh-3.2# e2label /dev/sda2 /boot sh-3.2# e2label /dev/sda3 /boot Expected results: Different labels.
Comment 1 Charles R. Anderson 2008-02-07 20:28:04 EST
Candidates for fixing this are filed as Bug #364441, Bug #364451. I like the idea of using UUIDs instead of LABELs.
Comment 2 Jeremy Katz 2008-02-24 16:19:31 EST
We're going to switch to using UUIDs (I committed that today), but we still shouldn't create duplicate labels. There was a bug around the time of the alpha which could have led to duplicate labels and I think it should be resolved now. Have you seen this more recently?
Comment 3 Jesse Keating 2008-04-01 16:41:23 EDT
No response in over a month. Closing.