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: Sun, 10 May 2020 22:06:23 +0000 [thread overview]
Message-ID: <bug-207635-13602-CYU6UVhBGv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207635-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207635
Eric Biggers (ebiggers3@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebiggers3@gmail.com
--- Comment #3 from Eric Biggers (ebiggers3@gmail.com) ---
It sounds like the problem is that one of the inodes on your filesystem was
previously corrupted in such a way that it had unknown flags set.
Then one of these flags was assigned a meaning, causing things to break.
Running e2fsck v1.45.4 or later on the filesystem should fix this by clearing
the casefold flag. Can you try that?
I'm not sure there's anything else to do here, unless we were to make the
kernel ignore unexpected flags. Ted, have you considered that? And it is
intentional that e2fsck ignores unknown flags?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-05-10 22:06 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 [this message]
2020-05-11 16:24 ` bugzilla-daemon
2020-05-11 16:30 ` bugzilla-daemon
2020-05-11 16:59 ` bugzilla-daemon
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-CYU6UVhBGv@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).