Bug 494134
| Summary: | anaconda blanks out disk label on reformat | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tom Horsley <horsley1953> |
| Component: | anaconda | Assignee: | David Lehman <dlehman> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | pjones, rmaximo, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-04-14 20:15:03 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: | 472555 | ||
|
Description
Tom Horsley
2009-04-04 22:28:17 UTC
The label is part of the filesystem, which you have replaced. We are not creating labels any more because they are a poor solution to the problem of identifying devices by some means other than the device node name. We use UUIDs instead. It depends on what you do as to which ID is or is not a poor solution. UUIDs can be just as poor: If you replace a disk and reinstall, the UUIDs will all be different, you can manually recreate the same labels you used to have, but recreating UUIDs isn't as easy. Every possible disk identifier will turn out to be a pain in the patoot for someone under some circumstance :-). That is exactly the reason we stopped using labels -- you can easily end up with the same label on several different devices, which is usually not desirable. UUIDs, by definition, should be unique. You should avoid the practice of intentionally setting up duplicate UUIDs on multiple devices We use UUIDs to come as close as possible to ensuring that we are referring to the specific device we mean to refer to. You want to be able to change the devices without changing their specifications, but most users do not. We are intentionally being explicit about the exact device we refer to. If you do not want this behavior you are welcome to use labels instead. We just won't do it for you. OK, if I'm free to use labels, then I should be free to specify the label when I format the disk in anaconda, but it won't let me do that either. All I'm looking for is predictable behaviour when I install on a multi-boot system so I can have the new install's disk already setup to be mounted in my old boot partitions. If you are gonna wipe out the label, then the only possible predictable way to specify the disk is by using a device name like /dev/sda5, which is really undesirable. This doesn't seem like very exotic behaviour to me. (And invoking the magic distro-jealousy principle, I'd point out that the ubuntu and opensuse installers do let you specify labels and even let you say which disk identifier you'd like in the fstab file :-). |