------- Comment From [email protected] 2019-03-11 08:22 EDT------- The message "Device size is not aligned to the requested sector size." is because the size of your loopback device is not a multiple of 4096 bytes. With --sector-size 4096, it's size must be a multiple of 4096 bytes, otherwise you would a half sector at the end of the device.
Besides the setup with cryptsetup and 4K sector size, you can also try to setup your loopback devices with different sector sizes (and omit dm-crypt/cryptsetup totally). By default loopback devices use a physical block size of 512, however, you can create them with -b 4096 to get a loopback device with 4K physical block size. With that you should also be able to reproduce this. BTW: Please also see the thread about this topic on the LVM Mailing list that I have started in parallel, and especially the following post from David Teigland: https://www.redhat.com/archives/linux-lvm/2019-March/msg00018.html There is also already a draft patch from David Teigland for this in a private branch of the LVM2 git repository: https://sourceware.org/git/?p=lvm2.git;a=commit;h=dd6ff9e3a75801fc5c6166aa0983fa8df098e91a I hope that this fix will make it into the master branch at some point in time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817097 Title: pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1817097/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
