If I resize active logical volume using blivet, it leaves the volume deactivated. I can see in blivet log: INFO:blivet: executing action: [0] Resize Device (Grow) lvmlv test-1 (id 7) DEBUG:blivet: LVMLogicalVolumeDevice.resize: test-1 ; status: True ; DEBUG:blivet: LVMLogicalVolumeDevice.teardown: test-1 ; status: True ; controllable: True ; INFO:program: Running... udevadm settle --timeout=300 DEBUG:program: Return code: 0 DEBUG:blivet: LVMLogicalVolumeDevice._teardown: test-1 ; status: True ; controllable: True ; --> INFO:program: Running... lvm lvchange -a n test/1 DEBUG:program: Return code: 0 DEBUG:blivet: LVMVolumeGroupDevice.setupParents: kids: 1 ; name: test ; orig: True ; DEBUG:blivet: PartitionDevice.setup: sdb1 ; status: True ; controllable: True ; orig: True ; DEBUG:blivet: LVMPhysicalVolume.setup: device: /dev/sdb1 ; status: False ; type: lvmpv ; DEBUG:blivet: LVMVolumeGroupDevice.setupParents: kids: 1 ; name: test ; orig: True ; DEBUG:blivet: PartitionDevice.setup: sdb1 ; status: True ; controllable: True ; orig: True ; DEBUG:blivet: LVMPhysicalVolume.setup: device: /dev/sdb1 ; status: False ; type: lvmpv ; INFO:program: Running... udevadm settle --timeout=300 DEBUG:program: Return code: 0 --> INFO:program: Running... lvm lvresize --force -L 60m test/1 INFO:program: File descriptor 10 (/dev/mapper/control) leaked on lvm invocation. Parent PID 10520: /usr/bin/python INFO:program: File descriptor 13 (/dev/null) leaked on lvm invocation. Parent PID 10520: /usr/bin/python INFO:program: Extending logical volume 1 to 60.00 MiB INFO:program: Logical volume 1 successfully resized DEBUG:program: Return code: 0 INFO:program: Running... udevadm settle --timeout=300 DEBUG:program: Return code: 0 Version-Release number of selected component (if applicable): python-blivet-0.13-1.fc20.noarch How reproducible: always Steps to Reproduce: Use this script ('b' is Blivet instance, 'blivet' is the blivet module): lv = b.lvs[0] action = blivet.deviceaction.ActionResizeDevice(lv, 60) b.devicetree.registerAction(action) b.devicetree.processActions(dryRun=False)
I can not reproduce. Please verify that it still occurs in current version and if it does...please be as specific as possible about initial lvm setup. Thanks! - mulhern
Probably fixed by bz#1064898 fix.