Hi,
# virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home prop-1.img prop-expand.img command line: virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home prop-1.img prop-expand.img Examining prop-1.img ... libguestfs: trace: add_drive "prop-1.img" "readonly:true" libguestfs: trace: add_drive = 0 libguestfs: trace: add_drive "prop-expand.img" "readonly:false" libguestfs: trace: add_drive = 0 libguestfs: trace: launch libguestfs: trace: get_tmpdir libguestfs: trace: get_tmpdir = "/tmp" libguestfs: trace: get_cachedir libguestfs: trace: get_cachedir = "/var/tmp" libguestfs: trace: disk_format "/var/lib/libvirt/images/prop-expand.img" libguestfs: trace: disk_format = "raw" libguestfs: trace: get_cachedir libguestfs: trace: get_cachedir = "/var/tmp" [...] 100% --:-- libguestfs: trace: launch = 0 libguestfs: trace: lvm_set_filter "/dev/sda" libguestfs: trace: lvm_set_filter = -1 (error) Fatal error: exception Guestfs.Error("lvm_set_filter: vgchange: Couldn't find device with uuid zouQ8X-qxqJ-mp6p-pzg3-mi2i-K9YM-A763Kc. Refusing activation of partial LV home. Use --partial to override. Refusing activation of partial LV swap. Use --partial to override. R libguestfs: trace: close libguestfs: trace: internal_autosync libguestfs: trace: internal_autosync = 0
I don't understand this error message. I also see that vgchange doesn't even have a 'partial' option, so I'm not sure how to troubleshoot it. Here is the filesystem layout for this system:
Which version of libguestfs, and where did you install it from?
It was installed via yum on fedora18:
# rpm -qva|grep guest libguestfs-tools-c-1.20.9-1.fc18.x86_64 libguestfs-tools-1.20.9-1.fc18.x86_64 libguestfs-1.20.9-1.fc18.x86_64
OK, in that case it's (unfortunately) not what I was thinking it was :-(
If you set:
export LIBGUESTFS_DEBUG=1
before running virt-resize then you will get a huge amount of extra debugging, which could be very valuable. If you post that lot somewhere it would be helpful.
However it's definitely a bug of some sort. I will open a Bugzilla bug later unless you get there first.
It's going to take me a bit of time to retest this with debugging info. This happened during a production change window I was given for this. I have the images backed up on another server for testing, but will take me a day or two. I'd appreciate it if you would open the bug to get us started and in front of some other people... Come to think of it, considering it's a bug, how are other people resizing VMs with LVM partitions? Should I plan to find an alternate method to do this? Thanks, Alex