Red Hat Bugzilla – Bug 138824
system-config-lvm fails around editing fstab
Last modified: 2007-11-30 17:07:14 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020
Description of problem:
system-config-lvm fails to create a logical volume and produces a
GtkDeprecationWarning: gtk.mainloop is deprecated, use gtk.main instead
Traceback (most recent call last):
File "/usr/share/system-config-lvm/InputController.py", line 654, in
new_lv_command_set[NEW_FSTAB_ARG] = FSTAB_entry
NameError: global name 'NEW_FSTAB_ARG' is not defined
There's also a relatively minor layout issue -- see the screenshot I'm
going to attach in a minute.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. (See attached screenshot)
2. Click on the OK button.
Actual Results: No logical volume created.
Expected Results: A logical volume to be created and an entry written
I did think that perhaps it was attempting to create a very small
logical volume (8Mb, I actually meant 8Gb) but when I repeated the
exercise with a properly sized logical volume it still failed. It
wasn't until I unchecked the "Check here if you wold like an entry to
be made in /etc/fstab" box that I could create the logical volume.
Since the most tedious part (for me) of creating a new logical volume
is editing /etc/fstab this does rather tend to render the tool less
than useful :-)
Created attachment 106496 [details]
Screenshot of LVM creation dialog box
The automatic creation of an fstab entry feature is being pulled for
the initial release and has been put in feature tracker for U1.
That's a shame -- it's the one feature I liked (being a bit of a
veteran of the lvm command line).
Just to let you know, it will not be lost, and if it can be squeezed
in it might make it in the initial release yet. There is just a
dwindling amount of time to insure it is adequately tested -- I think
any part of an application that writes to an important /etc file that
is read on startup had better work with no flaws.