Bug 444180 - lvrename command fails to update /etc/fstab
Summary: lvrename command fails to update /etc/fstab
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lvm2
Version: 5.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: Corey Marthaler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-25 17:34 UTC by Kevin L
Modified: 2010-05-13 13:58 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-13 13:58:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kevin L 2008-04-25 17:34:39 UTC
Description of problem:
When you use lvrename to rename a logical volume, it does not automatically 
update the corresponding entry in the /etc/fstab. Granted this is more of an 
enhancement request, but if you forget to modify the entry in /etc/fstab file 
before rebooting, it will fail to mount on reboot. It gets even better if you 
rename the root logical volume because in addition to the above you also need 
to modify the grub.conf :)


Version-Release number of selected component (if applicable):
Any RHEL version, but tested on 5.x


How reproducible:
Always

Steps to Reproduce:
1.use lvrename to rename a logical volume
2.reboot
3.system fails to mount the filesystem because /etc/fstab was not updated
  
Actual results:
renamed filesystem does not mount

Expected results:
system should boot with the properly renamed logical volume

Additional info:
none

Comment 1 Kevin L 2008-04-25 17:40:00 UTC
Also, this logic would most likely apply to all the rename commands in lvm2.

Comment 3 Zdenek Kabelac 2010-05-13 13:58:53 UTC
lvrename tool is low level tool - you most probably want to use some higher level user-space oriented tool like system-config-lvm. This tool should also handle /etc/fstab changes.


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