|
Bugzilla – Full Text Bug Listing |
| Summary: | Unable to edit fstab with unused duplicat volume label | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Seymour Metz <smetz3> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Minor | ||
| Priority: | P5 - None | ||
| Version: | Leap 15.2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Error popup
Partition list |
||
Created attachment 840419 [details]
Partition list
Note that while Smedley appears on two partitions, only one has a mount point.
The first attachment doesn't look like an error popup to me. Anyway, please always attach complete yast logs. To collect log files run 'save_y2logs' and attach the log file archive this command creates (usually named /tmp/y2log-SOMETHING.tar.xz). That said, duplicate volume labels are a bad thing, independent of whether or not they are acually used in fstab. For one, mount by label will have unpredictable results and second, the symlinks udev maintains in /dev/disk/by-label/ will turn messy. If you just dd'ed the partitions around I would expect the same to hold for the UUID. Nothing we can do, I guess. Closing bug. |
Created attachment 840418 [details] Error popup I was attempting to use the Yast2 partitioner to add the nofail option to some JFC volumes. Copies of htese volumes exist on an SSD and a disk, but only the ones on the SSD have assigned mount points. In all cases but one, the partioner completed normally. For one volume (/dev/sda14) the partitioner complained about a duplicate volume label. Note that I should be able to get around this by changing the volume label on the unmounted copy.