** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Ff-series)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1847340
Title:
ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Disco:
New
Status in linux source package in Eoan:
New
Status in linux source package in FF-Series:
New
Bug description:
[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.
[Test Case]
Forcibly power cycle a system running 'stress-ng --dir 0'. I've created a
package to automate the reproduction:
https://git.launchpad.net/~dannf/+git/dgx2-ext4-csum-repro?h=master
[Fix]
[Regression Risk]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
