https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #243 from Han Vinke (jfavinke@xxxxxxxxx) --- I have a PC with multiple boot -Windows 10, Arch linux with kernel 4.19.x en Ubuntu Disco Dingo with 4.19.x. My Arch linux is an encrypted LVM. I can actually invoke the EXT4-fs errors on Ubuntu! Which is not encrypted but has cryptsetup-initramfs installed, because I make regular backups with partclone from the Arch partitions. All that is needed on Ubuntu is to run sudo update-initramfs -u cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'crypsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. You will get a warning or error that is also subscribed in this bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901830 The problem is that when you reboot you will get all the EXT4-fs errors. I have to do a e2fsck via Arch, it reports some inode errors and when rebooting Ubuntu the problem is gone, if there never were any problems. Also when I am on ARCH cloning the Ubuntu partitions I can reproduce these errors. When mistakenly partcloning a read-only mounted partition for instance. -- You are receiving this mail because: You are watching the assignee of the bug.
