From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.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
Date: Mon, 11 May 2020 16:59:00 +0000 [thread overview]
Message-ID: <bug-207635-13602-P7O80y9a2W@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207635-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207635
Christian Kujau (lists@nerdbynature.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lists@nerdbynature.de
--- Comment #6 from Christian Kujau (lists@nerdbynature.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.
next prev parent reply other threads:[~2020-05-11 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 9:07 [Bug 207635] New: EXT4-fs error (device sda3): ext4_lookup:1701: inode #...: comm find: casefold flag without casefold feature; EXT4-fs (sda3): Remounting filesystem read-only bugzilla-daemon
2020-05-09 9:13 ` [Bug 207635] " bugzilla-daemon
2020-05-10 20:37 ` bugzilla-daemon
2020-05-10 22:06 ` bugzilla-daemon
2020-05-11 16:24 ` bugzilla-daemon
2020-05-11 16:30 ` bugzilla-daemon
2020-05-11 16:59 ` bugzilla-daemon [this message]
2020-05-11 18:26 ` bugzilla-daemon
2020-05-12 0:55 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-207635-13602-P7O80y9a2W@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.