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 20:19:34 +0000 [thread overview]
Message-ID: <bug-216162-202145-X2asmUYg2g@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216162-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216162
--- Comment #10 from ghtm2@protonmail.com ---
Which f2fs-tools are those?
On my end neither f2fs-tools-1.15 nor f2fs-tools-git commit
c1144bf472f69fdfac8f3fd7634aab19b771c32e fix anything.
This is the output:
Info: MKFS version
"Linux version 5.13.6-arch1-1 (linux@archlinux) (gcc (GCC) 11.1.0, GNU ld
(GNU Binutils) 2.36.1) #1 SMP PREEMPT Thu, 29 Jul 2021 00:21:06 +0000"
Info: FSCK version
from "Linux version 5.13.6-arch1-1 (linux@archlinux) (gcc (GCC) 11.1.0, GNU
ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Thu, 29 Jul 2021 00:21:06 +0000"
to "Linux version 5.18.7-arch1-1 (linux@archlinux) (gcc (GCC) 12.1.0, GNU
ld (GNU Binutils) 2.38) #1 SMP PREEMPT_DYNAMIC Sat, 25 Jun 2022 20:22:01 +0000"
Info: superblock features = 2828 : extra_attr inode_checksum sb_checksum
compression
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: Segments per section = 1
Info: Sections per zone = 1
Info: total FS sectors = 262144 (128 MB)
Info: CKPT version = 1a027a03
Info: Checked valid nat_bits in checkpoint
Info: checkpoint state = d5 : nat_bits crc fsck compacted_summary unmount
[FSCK] Check node 1 / 1282 (0.08%)
[FSCK] Check node 129 / 1282 (10.08%)
[FSCK] Check node 257 / 1282 (20.08%)
[FSCK] Check node 385 / 1282 (30.08%)
[FSCK] Check node 513 / 1282 (40.08%)
[FSCK] Check node 641 / 1282 (50.08%)
[FSCK] Check node 769 / 1282 (60.08%)
[FSCK] Check node 897 / 1282 (70.08%)
[FSCK] Check node 1025 / 1282 (80.08%)
[FSCK] Check node 1153 / 1282 (90.08%)
[FSCK] Check node 1281 / 1282 (100.08%)
[FSCK] Max image size: 36 MB, Free space: 52 MB
[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Ok..] [0x9be]
[FSCK] valid_node_count matching with CP (de lookup) [Ok..] [0x502]
[FSCK] valid_node_count matching with CP (nat lookup) [Ok..] [0x502]
[FSCK] valid_inode_count matched with CP [Ok..] [0x502]
[FSCK] free segment_count matched with CP [Ok..] [0x2f]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Ok..]
Done: 0.000000 secs
I've updated the broken image attached to this bug report.
--
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 20:19 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
2022-07-17 20:17 ` bugzilla-daemon
2022-07-17 20:19 ` bugzilla-daemon [this message]
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-X2asmUYg2g@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.