> > # 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?

> >> > # 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.

> >> >> > # 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. Does this guest have multiple disks?

> Yes, here's the layout from the vm: > > # df -h > Filesystem Size Used Avail Use% Mounted on > devtmpfs 7.9G 0 7.9G 0% /dev > tmpfs 7.9G 0 7.9G 0% /dev/shm > tmpfs 7.9G 643M 7.3G 9% /run > tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup > /dev/mapper/prop-root 15G 11G 2.9G 79% / > tmpfs 7.9G 12K 7.9G 1% /tmp > /dev/mapper/prop-boot 477M 95M 358M 21% /boot > /dev/mapper/prop-home 222G 215G 7.6G 97% /home > > I'll add this info to the bug report. Just to be clear, it has multiple virtual block devices, eg. /dev/vda and /dev/vdb ...? This isn't (currently) a supported configuration for virt-resize, although it ought to be.

Hi, >> Yes, here's the layout from the vm: >> >> # df -h >> Filesystem Size Used Avail Use% Mounted on >> devtmpfs 7.9G 0 7.9G 0% /dev >> tmpfs 7.9G 0 7.9G 0% /dev/shm >> tmpfs 7.9G 643M 7.3G 9% /run >> tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup >> /dev/mapper/prop-root 15G 11G 2.9G 79% / >> tmpfs 7.9G 12K 7.9G 1% /tmp >> /dev/mapper/prop-boot 477M 95M 358M 21% /boot >> /dev/mapper/prop-home 222G 215G 7.6G 97% /home >> >> I'll add this info to the bug report. > > Just to be clear, it has multiple virtual block devices, eg. > /dev/vda and /dev/vdb ...? > > This isn't (currently) a supported configuration for virt-resize, > although it ought to be. Yes, that's correct - vda and vdb. Not sure how I missed that previously. Can I perform the steps that virt-resize executes manually instead, and either perform it only on the one to be resized or otherwise adjust the arguments accordingly? Is it documented?

<fs> add-ro prop-1.img # sda <fs> add-ro prop-2.img # sdb <fs> sparse prop-expand.img <SIZE> # sdc <fs> run <fs> part-list /dev/sda

<fs> part-init /dev/sdc mbr <fs> part-add /dev/sdc p <#1...> <fs> part-add /dev/sdc p <#2...> <fs> pvcreate /dev/sdc2 <fs> vgcreate prop2 /dev/sdc2 <fs> lvcreate root prop2 <#3> <fs> lvcreate-free home prop2 100

<fs> copy-device-to-device /dev/prop/root /dev/prop2/root <fs> resize2fs /dev/prop2/root