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: Sun, 17 Jul 2022 04:03:36 +0000 [thread overview]
Message-ID: <bug-216162-202145-wOHtfuePvW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216162-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216162
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chao@kernel.org
--- Comment #8 from Chao Yu (chao@kernel.org) ---
(In reply to ghtm2 from comment #5)
> According to git bisect that I just ran,
> 198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8 is the first bad commit.
> "f2fs: fix to do sanity check for inline inode"
>
> I reverted that on linux-stable v5.18.9 and the problem is indeed no longer
> present.
>
> Wile doing that I've found that my initial description as well es the
> attached image were missing a command:
> chattr -R +c /mnt/etc
> Without it the compression wouldn't be enabled and the errors wouldn't be
> visible.
I can reproduce your issue and repair this w/ last f2fs-tools:
[reproduce]
mount -o loop ./broken.img /mnt/f2fs/
touch /mnt/f2fs/file
lsattr /mnt/f2fs/file
-----------------N-- /mnt/f2fs/file
chattr +c /mnt/f2fs/file
lsattr /mnt/f2fs/file
--------c--------N-- /mnt/f2fs/file
umount /mnt/f2fs
mount -o loop ./broken.img /mnt/f2fs/
lsattr /mnt/f2fs/file
lsattr: Structure needs cleaning while trying to stat /mnt/f2fs/file
[repair]
fsck.f2fs ./broken.img
output:
[FIX] (fsck_chk_inode_blk: 728) --> [0x505] i_flags=0x4 -> 0x0
[ASSERT] (fsck_chk_inode_blk:1182) --> ino: 0x505 chksum:0xe7b707a8, but
calculated one is: 0x3f6daf58
[FIX] (fsck_chk_inode_blk:1188) --> ino: 0x505 recover, i_inode_checksum=
0xe7b707a8 -> 0x3f6daf58
[verify]
mount -o loop ./broken.img /mnt/f2fs/
stat /mnt/f2fs/file
File: /mnt/f2fs/file
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 70fh/1807d Inode: 1285 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-07-17 11:51:41.705230802 +0800
Modify: 2022-07-17 11:51:41.705230802 +0800
Change: 2022-07-17 11:51:57.641110482 +0800
Birth: -
lsattr /mnt/f2fs/file
-----------------N-- /mnt/f2fs/file ---- compressed flag was removed by
fsck.
--
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-17 4:04 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
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 [this message]
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-wOHtfuePvW@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.