+++ This bug was initially created as a clone of Bug #584985 +++ Description of problem: I try to change size of a lvm volume with system-config-lvm and wondering if the option in settings dialog is therefore. Version-Release number of selected component (if applicable): system-config-lvm-1.1.12-2.fc13.noarch How reproducible: Always. Steps to Reproduce: 1. Click on button "edit settings" of a lvm volume (for example "backup") 2. Change size of the volume (for example 10G -> 20G) 3. Click on OK Actual results: Nothing happens in the dialog, but in console you can see the traceback. Expected results: New size was applied and volume is remounted. Additional info: Traceback (most recent call last): File "/usr/share/system-config-lvm/InputController.py", line 1061, in on_edit_lv if dlg.run() == False: File "/usr/share/system-config-lvm/InputController.py", line 1351, in run if self.apply() == True: File "/usr/share/system-config-lvm/InputController.py", line 2150, in apply self.command_handler.mount(lv_path, tmp_mountpoint) TypeError: mount() takes exactly 4 arguments (3 given) Output of lvdisplay: --- Logical volume --- LV Name /dev/vol/backup VG Name vol LV UUID X3VXrt-Unov-cVvN-hk1C-1cW9-SEDI-nRK4f5 LV Write Access read/write LV Status available # open 0 LV Size 10,00 GiB Current LE 2560 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 --- Logical volume --- LV Name /dev/vol/vm VG Name vol LV UUID 3kYzVd-WdKM-Klx1-t7TQ-fpmA-v2se-jyrrZm LV Write Access read/write LV Status available # open 1 LV Size 100,00 GiB Current LE 25600 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:2 --- Logical volume --- LV Name /dev/vg_spritty/lv_root VG Name vg_spritty LV UUID UN3Y9d-GvY2-eMqx-v6on-2qUG-YZzz-AqRjMq LV Write Access read/write LV Status available # open 1 LV Size 50,00 GiB Current LE 1600 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 --- Logical volume --- LV Name /dev/vg_spritty/lv_home VG Name vg_spritty LV UUID JCPUGD-8waM-ybtn-JW8M-GEgK-MmWu-FQ3Bxt LV Write Access read/write LV Status available # open 1 LV Size 176,78 GiB Current LE 5657 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:3 --- Logical volume --- LV Name /dev/vg_spritty/lv_swap VG Name vg_spritty LV UUID uRJ2gA-fq2t-30wJ-xyz2-4sxn-2aCC-gjhZhx LV Write Access read/write LV Status available # open 1 LV Size 5,59 GiB Current LE 179 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:4 --- Additional comment from raphgro on 2010-04-22 16:23:16 EDT --- Created an attachment (id=408438) /etc/fstab
Fixed in upstream: http://git.fedorahosted.org/git/?p=system-config-lvm.git;a=commit;h=b1b25c5d5388bce21c915e922454a1b1d5d047dd
Second patch is also in upstream: http://git.fedorahosted.org/git/?p=system-config-lvm.git;a=commit;h=1aaa5a0e7cb6f8abe02ca320ad28f7ff3d1c845b
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. New Contents: Prior to this update, an attempt to adjust the size of a logical volume failed, and a traceback was written to standard error. With this update, the size changes are applied, and relevant volumes are correctly remounted.
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. http://rhn.redhat.com/errata/RHBA-2011-0103.html