Bug 429784 - anaconda created a new filesystem with the same label as existing
Summary: anaconda created a new filesystem with the same label as existing
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F9Blocker
TreeView+ depends on / blocked
 
Reported: 2008-01-22 23:31 UTC by Charles R. Anderson
Modified: 2008-08-02 23:40 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-04-01 20:41:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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.


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