https://bugzilla.kernel.org/show_bug.cgi?id=207635 --- Comment #4 from Joerg M. Sigle (joerg.sigle@xxxxxxxxxx) --- Hi Eric - thanks for your quick & helpful response. Your explanation sounds plausible; now I also understand why the problem was persistent: The e2fsck of my distribution was 1.44. If it is too old for these problems, setting the fs to ro and marking it for an fsck on next reboot simply could not achieve anything. Me manually overwriting the default kernel version in grub.cfg with 5.3.15, was also short lived: because grub.cfg gets rewritten during various apt updates. This is why the problem kept coming back even when I did not /knowingly/ switch back to a more recent kernel... Now I got the current master e2fsck from github - thank you tytso. This may hopefully have found and fixed the problem: e2fsck 1.46-WIP (20-Mar-2020) Pass 1: Checking inodes, blocks, and sizes Inode 4244276 has encrypt flag but no encryption extended attribute. Clear flag<y>? yes Inode 4253945 has the casefold flag set but is not a directory. Clear flag<y>? yes Inode 4253945 has encrypt flag but no encryption extended attribute. Clear flag<y>? yes Pass 2: Checking directorry structure Pass 3: Checking directorry connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sda3: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sda3: ***** REBOOT SYSTEM ***** ... (The last mentioned inode is the same that caused the error message in the beginning of this thread.) Kind regards, Joerg -- You are receiving this mail because: You are watching the assignee of the bug.
