[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-207635-13602-P7O80y9a2W@https.bugzilla.kernel.org/>
Date: Mon, 11 May 2020 16:59:00 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 207635] EXT4-fs error (device sda3): ext4_lookup:1701: inode
#...: comm find: casefold flag without casefold feature; EXT4-fs (sda3):
Remounting filesystem read-only
https://bugzilla.kernel.org/show_bug.cgi?id=207635
Christian Kujau (lists@...dbynature.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lists@...dbynature.de
--- Comment #6 from Christian Kujau (lists@...dbynature.de) ---
(In reply to Joerg M. Sigle from comment #5)
> The same person might run a kernel with casefold and/or encryption disabled
> on Tuesday. So, would it really be necessary to set their filesystem to ro -
I don't know about the inner workings of this particular issue here, but
turning the filesystem to RO when errors are encountered - isn't this what the
"error-behavior" flag controls?
$ tune2fs -l /dev/sda1 | grep ^Err
Errors behavior: Remount read-only
Setting this to "continue" or "panic" should have avoided that whole "RO"
situation, I guess.
--
You are receiving this mail because:
You are watching the assignee of the bug.
Powered by blists - more mailing lists