Red Hat Bugzilla – Bug 586553
extending a logical volume creates a duplicate entry in /etc/fstab
Last modified: 2016-04-26 11:50:44 EDT
+++ This bug was initially created as a clone of Bug #571302 +++
Created an attachment (id=398413)
recreated /etc/fstab file as it appeared after extending the LV
Description of problem:I had extended one of my logical volumes in my 1st volume group using the GUI /usr/bin/system-config-lvm. Upon first reboot I saw the following;
Mounting local filesystems: mount: /dev/mapper/ncc1701_01-var already mounted or /var busy
Both fsck and resize2fs came back ok. At the suggestion of dd_wizard, I checked my fstab file and found a duplicate entry had been made for that devices
Version-Release number of selected component (if applicable):
How reproducible:Haven't tried to do it again
Steps to Reproduce:
1.Launch system-config-lvm from menu
2.Select "Edit" of a LV and increase size of the LV
3.Apply changes and close system-config-lvm
4.Reboot and if you don't use graphic boot you will see the above error
Actual results:Error message indicating a failed attempt at mounting a filesystem on a LV
Expected results:Boot up witout any FAILED messages
Fixed in upstream:
Seems testable, I'll ask for more information if I can't reproduce the problem.
Marek, I had originally reported the same thing about 2 months back. Turned out that system-config-lvm created a duplicate entry for that filesystem in fstab. I haven't had a need to try it since the last update that was supposed to fix it, so I couldn't tell you if it actually fixed yet.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Previously, extending a logical volume may have caused the relevant line in the /etc/fstab file to be duplicated. This no longer occurs, and /etc/fstab is now processed as expected.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.