[linux-lvm] Underlying physical volume resized?!

[Gionatan Danti]

 > On 18/11/2016 04:43, Marian Csontos wrote:
>
> Hi, the warning was added only recently - commit c0912af3 added 2016-01-22:
>
> https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=c0912af3104cb72ea275d90b8b1d68a25a9ca48a

Ok, this explain why I only recently saw this warning

> Were the partitions created by anaconda?
> This might be an installer bug.
>
> LVM allows overriding PV size to be larger than device size.
>
> More about the feature here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1323950
>
> I do not think pvmove could help here, as there will be read errors on
> the device.

This a cloud VM not directly installed by me, rather from the cloud 
provider. I think they somewhat messed up their template partition table 
but, with no warning and no apparent error, the problem was unrecognized

> Deactivating swap (`swapoff /dev/$VG/$LV`)
> deleting the swap LV (`lvremove $VG/$LV`)
> shrinking the PV (simply running `pvresize /dev/sda2` without arguments),
> recreating the swap LV (`lvcreate -n $LV -L $SIZE $VG`),
> `mkswap /dev/$VG/$LV`
> and `swapon /dev/$VG/$LV`
> should do.

This is a production machine, so I am somewhat reluctant to shrink 
swap/physical volumes. From what I understand (and from my own testing 
on a test machine) this slight discrepancy between partition and PV 
*should* pose no problems to my setup. At most, when swap is full, I can 
receive an error about a failed page swapping.  Is this assumption correct?

Thank you very much.

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti at assyoma.it - info at assyoma.it
GPG public key ID: FF5F32A8