Hi, I'm trying to resize a 15GB LVM root partition on a fedora20 server with a fedora20 guest and I'm having a problem. Is this supported on fedora20? I recall having a similar problem (maybe even exact same problem) all the way back in fedora16 or fedora17, but hoped/thought it would be fixed by now? # virt-df -h test1-011015.img Filesystem Size Used Available Use% test1-011015.img:/dev/prop/boot 476M 109M 338M 23% test1-011015.img:/dev/prop/root 14G 10G 3.3G 72% # truncate -s 50G newimg # virt-resize test1-011015.img newimg --expand /dev/sda1 --LV-expand /dev/prop/root Examining test1-011015.img ... virt-resize: libguestfs error: lvm_set_filter: vgchange -ay: /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory Couldn't find device with uuid uA2ju5-EElD-xgB3-EE7J-gJ55-UnkY-Vq2l6H. /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory Refusing activation of partial LV home. Use --partial to override. What are my alternatives for resizing a root partition on LVM? Thanks, Alex
Michal Privoznik
2015-Jan-12 08:13 UTC
Re: [libvirt-users] Resizing lvm fails with fedora20
On 11.01.2015 02:57, Alex Regan wrote:> Hi, > I'm trying to resize a 15GB LVM root partition on a fedora20 server with > a fedora20 guest and I'm having a problem. Is this supported on fedora20? > > I recall having a similar problem (maybe even exact same problem) all > the way back in fedora16 or fedora17, but hoped/thought it would be > fixed by now? > > # virt-df -h test1-011015.img > Filesystem Size Used Available Use% > test1-011015.img:/dev/prop/boot 476M 109M 338M 23% > test1-011015.img:/dev/prop/root 14G 10G 3.3G 72% > > # truncate -s 50G newimg > # virt-resize test1-011015.img newimg --expand /dev/sda1 --LV-expand > /dev/prop/root > Examining test1-011015.img ... > virt-resize: libguestfs error: lvm_set_filter: vgchange -ay: > /run/lvm/lvmetad.socket: connect failed: No such file or directory > WARNING: Failed to connect to lvmetad: No such file or directory. > Falling back to internal scanning. > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > Couldn't find device with uuid uA2ju5-EElD-xgB3-EE7J-gJ55-UnkY-Vq2l6H. > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > /run/lvm/lvmetad.socket: connect failed: No such file or directory > Refusing activation of partial LV home. Use --partial to override. >I thought this has been already fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1016218> What are my alternatives for resizing a root partition on LVM?I guess updating lvm2. Seems like you won't be able to use pure vgchange and do thing by hand anyway. Michal
Hi, On 01/12/2015 03:13 AM, Michal Privoznik wrote:> On 11.01.2015 02:57, Alex Regan wrote: >> Hi, >> I'm trying to resize a 15GB LVM root partition on a fedora20 server with >> a fedora20 guest and I'm having a problem. Is this supported on fedora20? >> >> I recall having a similar problem (maybe even exact same problem) all >> the way back in fedora16 or fedora17, but hoped/thought it would be >> fixed by now? >> >> # virt-df -h test1-011015.img >> Filesystem Size Used Available Use% >> test1-011015.img:/dev/prop/boot 476M 109M 338M 23% >> test1-011015.img:/dev/prop/root 14G 10G 3.3G 72% >> >> # truncate -s 50G newimg >> # virt-resize test1-011015.img newimg --expand /dev/sda1 --LV-expand >> /dev/prop/root >> Examining test1-011015.img ... >> virt-resize: libguestfs error: lvm_set_filter: vgchange -ay: >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> WARNING: Failed to connect to lvmetad: No such file or directory. >> Falling back to internal scanning. >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> Couldn't find device with uuid uA2ju5-EElD-xgB3-EE7J-gJ55-UnkY-Vq2l6H. >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> /run/lvm/lvmetad.socket: connect failed: No such file or directory >> Refusing activation of partial LV home. Use --partial to override. >> > > I thought this has been already fixed: > > https://bugzilla.redhat.com/show_bug.cgi?id=1016218It looks like that only applies to RHEL6? Can you track down whether there was a fedora20 update for this?>> What are my alternatives for resizing a root partition on LVM? > > I guess updating lvm2. Seems like you won't be able to use pure vgchange > and do thing by hand anyway.Do you know where there is a HOWTO of some sort to do it using lvm from within the virtual machine? Is that even possible? Thanks, Alex> > Michal
Possibly Parallel Threads
- Re: Resizing lvm fails with fedora20
- [PATCH v2] daemon: Move lvmetad to early in the appliance boot process.
- [PATCH v2 0/4] Improve LVM handling in the appliance
- Re: [PATCH 2/3] New API: lvm_scan, deprecate vgscan (RHBZ#1602353).
- Windows XP sees fedora14/samba3 shares but not fedora20/samba4 shares