The fix for this bug was merged to the mainline kernel:
commit 8301c719a2bd ("fix null pointer dereference at
nilfs_segctor_do_construct()")
This commit was sent to the stable mailing list as well. (for v5.4+)
It also can be fixed by reverting the change corresponding to commit
c3aab9a0bd91
any updates on this bug? we still have problems and it makes the fs
unusable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868325
Title:
NILFS2 kernal crashes from normal use
To manage
Ubuntu Server 18.04 LTS – first crash: 15 may 2020
and 20.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868325
Title:
NILFS2 kernal crashes from normal use
To manage notifications about
Can the priority be upped? We have data sitting on the drive and afraid to
modify it for fear of data loss. We've seen crashes from reads as well, but
haven't identified the source, so we just leave it alone until it gets
fixed.
On Sat, May 16, 2020 at 4:00 PM Launchpad Bug Tracker <
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nilfs2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868325
Title:
Correction: I read /etc/issue to get lsb, but reading /etc/lsb-release
showed this bug actually was in the 18.04 LTS. The system had been
upgraded from the original 16.04.4 LTS via the do-release-upgrade and
/etc/issue retained the old version.
--
You received this bug notification because you
