------- Comment From [email protected] 2019-02-22 05:23 EDT------- Further investigations revealed that no dm-crypt mapper device is needed at all to reproduce the behaviour but just two block devices with different physical block sizes, e.g.
# blockdev --getpbsz /dev/mapper/mpatha-part1 512 # blockdev --getpbsz /dev/dasdc1 4096 Mind to first add the SCSI device/the device with the smaller phys. block size to the volume group when running the 'vgcreate' command. # blockdev --getpbsz /dev/mapper/TEST_VG-LV1 512 Use one SCSI disk partition (multipath devices are recommended but not required) and one DASD partition to recreate the pvmove problem. Run pvs after the move completed, and unmount, mount the fs again. The fsck.ext4 does not detect any problems on the fs which is unexpected. Pertaining syslog entries: Feb 22 11:09:23 system kernel: print_req_error: I/O error, dev dasdc, sector 280770 Feb 22 11:09:23 system kernel: Buffer I/O error on dev dm-3, logical block 139265, lost sync page write Feb 22 11:09:23 system kernel: JBD2: Error -5 detected when updating journal superblock for dm-3-8. Feb 22 11:09:23 system kernel: Aborting journal on device dm-3-8. Feb 22 11:09:23 system kernel: print_req_error: I/O error, dev dasdc, sector 280770 Feb 22 11:09:23 system kernel: Buffer I/O error on dev dm-3, logical block 139265, lost sync page write Feb 22 11:09:23 system kernel: JBD2: Error -5 detected when updating journal superblock for dm-3-8. Feb 22 11:09:23 system kernel: print_req_error: I/O error, dev dasdc, sector 2242 Feb 22 11:09:23 system kernel: Buffer I/O error on dev dm-3, logical block 1, lost sync page write Feb 22 11:09:23 system kernel: EXT4-fs (dm-3): I/O error while writing superblock Feb 22 11:09:23 system kernel: EXT4-fs error (device dm-3): ext4_put_super:938: Couldn't clean up the journal Feb 22 11:09:23 system kernel: EXT4-fs (dm-3): Remounting filesystem read-only Feb 22 11:09:23 system kernel: print_req_error: I/O error, dev dasdc, sector 2242 Feb 22 11:09:23 system kernel: Buffer I/O error on dev dm-3, logical block 1, lost sync page write Feb 22 11:09:23 system kernel: EXT4-fs (dm-3): I/O error while writing superblock Feb 22 11:09:32 system kernel: EXT4-fs (dm-3): bad block size 1024 The very last syslog line repeats upon 'mount /dev/mapper/TEST_VG-LV1 /mnt ' attempts, the 1024 block size is related to # blockdev --getbsz /dev/mapper/TEST_VG-LV1 1024 After the pvmove the physical blocksize is also changed to # blockdev --getpbsz /dev/mapper/TEST_VG-LV1 4096 -- 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
