Bug 199697
Summary: | Doesn't react well to missing paths | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Bastien Nocera <bnocera> |
Component: | e2fsprogs | Assignee: | Eric Sandeen <esandeen> |
Status: | CLOSED NOTABUG | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 4.0 | CC: | kzak, sct, srevivo |
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-02-12 22:11:35 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: | 198694, 205159, 234251, 236329 |
Description
Bastien Nocera
2006-07-21 13:40:33 UTC
Labels should be unique on your system. If you are using a label more than once, then it is required to use the first entry in the list to be consistent. I think it is not a good idea if blkid takes the first in the list which is physically available, because this could result in a partition switch, which would be very bad, e.g. if you switch /tmp with /home, because /tmp is not there and both partitions have the same label. I could only say: DO not use labels with multipath or software-raid. > I could only say: DO not use labels with multipath or software-raid.
Anaconda will take labels, if a filesystem is on the real devices.
Also, the concept of using label is handling filesystem well even if the
physical device name is changed, right ?
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. For lack of a better resolution type, NOTABUGging this one based on the IT closing; also, from my understanding, we have a by-label entry in fstab for which there is no device containing that label, and fsck stops. This looks to me like simply a misconfiguration.... |