https://bugzilla.kernel.org/show_bug.cgi?id=207635 Bug ID: 207635 Summary: EXT4-fs error (device sda3): ext4_lookup:1701: inode #...: comm find: casefold flag without casefold feature; EXT4-fs (sda3): Remounting filesystem read-only Product: File System Version: 2.5 Kernel Version: 5.5.11 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: ext4 Assignee: fs_ext4@xxxxxxxxxxxxxxxxxxxx Reporter: joerg.sigle@xxxxxxxxxx Regression: No Hello. Since upgrade to Linux 5.5.11 on a Devuan System I've had a previously completely stable system repeatedly remount the root file system as read only, effectively requiring a reboot and fsck. This problem appeared at about the same time when I read about the casefold feature being added; I did not willingly activate that feature nor do I want to use it. I suspect however, that the new feature might have come with a new bug. This is an ext2 filesystem using the ext4 kernel subsystem. The error occurs maybe once every few days; i.e. I'm practically unable to reproduce it willingly, but it's often enough to recognize it as a truly existing problem. It's definitely a show-stopper, but I don't know yet whether it causes data loss as well. Going back to the previously used Linux 5.3.15 quite probably removed the problem. And going forward to 5.5.11 made the problem re-appear. These are self compiled kernels, quite possibly I don't use the best .config that I could. I can provide the .config files for both the 5.3.15 and the 5.5.11 kernels I have used. $ cat /proc/version Linux version 5.5.11-i7 (root@think3) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PREEMPT Wed Mar 25 04:44:37 CET 2020 # dmesg | tail EXT4-fs error (device sda3): ext4_lookup:1701: inode #4253945: comm find: casefold flag without casefold feature EXT4-fs (sda3): Remounting filesystem read-only This was after startup, a little bit of web browsing, and getting and reading my e-mail. And upon restart: /dev/sda3 contains a file system with errors, check forced. /dev/sda3: Deleted inode 14729236 has zero dtime. FIXED. /dev/sda3: Deleted inode 14729243 has zero dtime. FIXED. /dev/sda3: Deleted inode 14738534 has zero dtime. FIXED. /dev/sda3: Deleted inode 14738583 has zero dtime. FIXED. /dev/sda3: Deleted inode 14738843 has zero dtime. FIXED. Thanks a lot for looking into this; and I may provide additional info if you tell me what you need. Kind regards - j. -- You are receiving this mail because: You are watching the assignee of the bug.
