[Impact]
In the event of a loss of power, ext4 filesystems mounted w/ data=journal,journal_checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media.
[Impact] journal_ checksum are subject to a corruption issue that requires a fsck to recover. This is exacerbated by installations by curtin that set passno=0 in /etc/fstab, preventing fsck from running automatically and thus requiring a manual recovery. And *that* is further exacerbated because initramfs-tools is smart enough to not include fsck.ext4 when passno=0 is detected in /etc/fstab, requiring the user to boot from recovery media.
In the event of a loss of power, ext4 filesystems mounted w/ data=journal,
[Test Case] /git.launchpad. net/~dannf/ +git/dgx2- ext4-csum- repro?h= master
Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a package to automate the reproduction:
https:/
[Fix]
[Regression Risk]