Description of problem:
system-config-lvm allows resizing of live mounted volumes including root!, and fails to change anything in the underlying filesystem. This causes fs errors on bootup and possible loss of data.
Version-Release number of selected component (if applicable):
1.1.4 in Fedora 10
Steps to Reproduce:
1. start system-config-lvm tool, select a LV, click "Edit Properties"
2. reduce the size of the LV, exit tool, and reboot
3. what the fs errors at boot time, and pray you haven't just lost your files
it just does a shrink on the LV
I was sure it would unmount the fs, do a fsck, and resize2fs, then lvreduce, then resize2fs again, and mount back. thats the purpose of a tool
I just thought i'd mention that this is with an encrypted LVM. resize2fs doesnt seem to work either. Maybe the tool needs to be adjusted for LUKS encryption?
Updated package should be in F10 soon (pushed to stable), one problem with resize2fs was fixed. Shrinking root filesystem should be possible also on mounted filesystem.
I will check that problem with encrypted filesystem, but next week I'm leaving for holidays, so it will be fixed in late September at best.
well, it didn't seem to help any of the problems above. resize2fs doesn't work either, but on the non encrypted volume it does work. So its definitely a problem in resize2fs, and the LVM tool is practically useless at this point.
# resize2fs /dev/VolGroup00/LVspare
resize2fs 1.41.4 (27-Jan-2009)
resize2fs: Device or resource busy while trying to open /dev/VolGroup00/LVspare
Couldn't find valid filesystem superblock.
I think I see the problem now, It looks like resize2fs needs to operate on the luks encrypted device only.
# ls /dev/mapper
So I guess the LVM tool just needs to be adjusted for this, for encrypted volumes. I tested that resize2fs works fine. I think the cryptsetup command would be required also. Just let me know if you need any more info at all.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Corruption of filesystem is cloned to bz#547363. There is no plan to support encrypted volumes in s-c-lvm as it is deprecated product. If you want to write a patch, i don't have a problem with adding it to upstream.