From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 216162] F2FS filesystem with compression broken after kernel version 5.18.1
Date: Sat, 02 Jul 2022 23:55:02 +0000 [thread overview]
Message-ID: <bug-216162-202145-kQzCGYjzwO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216162-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216162
Jaegeuk Kim (jaegeuk@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jaegeuk@kernel.org
--- Comment #3 from Jaegeuk Kim (jaegeuk@kernel.org) ---
I suspect one issue recent reported with respect to compression vs.
inline_data. Could you please run fsck from this?
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/log/?h=dev
Especially this patch should fix the corruption.
"fsck.f2fs: drop compression bit if inline_data is set"
And, in order to avoid the runtime issue, we need this from Linus's tree.
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev&id=29eeafc661f283a7412ecf8d9899a5ffd0c80f59
I think v5.18 stable branch hasn't merge the fixes yet. By any chance, could
you please apply the below from the Linus tree on top of 5.18?
"f2fs: attach inline_data after setting compression"
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-07-02 23:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 8:02 [f2fs-dev] [Bug 216162] New: F2FS filesystem with compression broken after kernel version 5.18.1 bugzilla-daemon
2022-07-02 23:03 ` [f2fs-dev] [Bug 216162] " bugzilla-daemon
2022-07-02 23:03 ` bugzilla-daemon
2022-07-02 23:23 ` bugzilla-daemon
2022-07-02 23:55 ` bugzilla-daemon [this message]
2022-07-03 15:29 ` bugzilla-daemon
2022-07-04 15:38 ` bugzilla-daemon
2022-07-11 13:31 ` bugzilla-daemon
2022-07-15 19:56 ` bugzilla-daemon
2022-07-17 4:03 ` bugzilla-daemon
2022-07-17 20:17 ` bugzilla-daemon
2022-07-17 20:19 ` bugzilla-daemon
2022-07-18 3:01 ` bugzilla-daemon
2022-07-18 7:42 ` 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-216162-202145-kQzCGYjzwO@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.