Bug 429784

Summary: anaconda created a new filesystem with the same label as existing
Product: [Fedora] Fedora Reporter: Charles R. Anderson <cra>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhide   
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: 2008-04-01 20:41:23 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:
Bug Depends On:    
Bug Blocks: 235706    

Description Charles R. Anderson 2008-01-22 23:31:56 UTC
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):
11.4.0.22-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-08 01:28:04 UTC
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 21:19:31 UTC
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 20:41:23 UTC
No response in over a month.  Closing.