[linux-lvm] Filesystem corruption with LVM's pvmove onto a PV with a larger physical block size

David Teigland teigland at redhat.com
Tue Mar 5 16:36:31 UTC 2019

On Tue, Mar 05, 2019 at 06:29:31PM +0200, Nir Soffer wrote:
> I don't this way of thinking is useful. If we go in this way, then write()
> should not
> let you write data, and later maybe the disk controller should avoid this?
> LVM is not a low level tool like dd. It is high level tool for managing
> device mapper,
> and providing high level tools to create user level abstractions. We can
> expect it
> to prevent system administrator from doing the wrong thing.
> Maybe LVM should let you mix PVs with different logical block size, but it
> should
> require --force.
> David, what do you think?

LVM needs to fix this, your solution sounds like the right one.

More information about the linux-lvm mailing list