Libguestfs - Jul 2013 - Re: [libvirt-users] Resize errors with virt-resize/vgchange

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

I've got 7.6G left. I think I'll attach a new disk with enough space
and copy the contents over so I can keep the system running. I'll
hopefully be able to work on the bug soon too.

Thanks,
Alex

On Wed, Jul 24, 2013 at 02:57:58PM -0400, Alex wrote:
> 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.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW

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?

Thanks,
Alex