[Libguestfs] guestfish emergency extension

[Richard W.M. Jones]

On Wed, May 19, 2021 at 10:01:33AM +0200, Gottschalk wrote:
> + lvm pvs
>   WARNING: Device /dev/sdb has size of 398267904 sectors which is smaller than corresponding PV size of 838860800 sectors. Was device resized?
>   WARNING: One or more devices used as PVs in VG vmail-vg have changed sizes.
>   PV         VG         Fmt  Attr PSize    PFree  
>   /dev/sda1  mailxxx-vg lvm2 a--   <20.00g      0 
>   /dev/sdb   vmail-vg   lvm2 a--  <400.00g      0 
>   /dev/sdc   vmail-vg   lvm2 a--  <400.00g 192.00m
> + lvm vgs
>   WARNING: Device /dev/sdb has size of 398267904 sectors which is smaller than corresponding PV size of 838860800 sectors. Was device resized?
>   WARNING: One or more devices used as PVs in VG vmail-vg have changed sizes.
>   VG         #PV #LV #SN Attr   VSize   VFree  
>   mailxxx-vg   1   2   0 wz--n- <20.00g      0 
>   vmail-vg     2   1   0 wz--n- 799.99g 192.00m
> + lvm lvs
>   WARNING: Device /dev/sdb has size of 398267904 sectors which is smaller than corresponding PV size of 838860800 sectors. Was device resized?
>   WARNING: One or more devices used as PVs in VG vmail-vg have changed sizes.
>   LV       VG         Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
>   root     mailxxx-vg -wi-a----- <19.04g                                                    
>   swap_1   mailxxx-vg -wi-a----- 980.00m                                                    
>   vmail-lv vmail-vg   -wi------- 799.80g

There's the error - the LVM PV is corrupt and/or the underlying disk
was shrunk without shrinking the PV.

Restoration from backups is the way to go here, but you could also try
examining the disk using the "virt-rescue" tool, which may allow you
to recover something.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html