[linux-lvm] Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size
mail at izyk.ru
Thu Feb 28 14:36:11 UTC 2019
> Discarding device blocks: done
> Creating filesystem with 307200 1k blocks and 76912 inodes
> # pvs
> /dev/LOOP_VG/LV: read failed after 0 of 1024 at 0: Invalid argument
> /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314507264: Invalid argument
> /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314564608: Invalid argument
> /dev/LOOP_VG/LV: read failed after 0 of 1024 at 4096: Invalid argument
> PV VG Fmt Attr PSize PFree
> /dev/loop0 LOOP_VG lvm2 a-- 496.00m 496.00m
> /dev/mapper/enc-loop LOOP_VG lvm2 a-- 492.00m 192.00m
> In case the filesystem of the logical volume is not mounted at the time of pvmove, it gets corrupted anyway, but you only see errors when trying to mount it.
It's because you FS had 1k blocks.
New device can't read with block 1k.
If you plan pvmove on device with 4k. Maybe you need make fs with:
"mkfs.ext4 -b 4096"
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3591 bytes
Desc: S/MIME Cryptographic Signature
More information about the linux-lvm