From: bugzilla-daemon--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 221229] New: F2FS partition enlargement with fscrypt not completed
Date: Sat, 14 Mar 2026 14:57:38 +0000 [thread overview]
Message-ID: <bug-221229-202145@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221229
Bug ID: 221229
Summary: F2FS partition enlargement with fscrypt not completed
Product: File System
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: f2fs
Assignee: filesystem_f2fs@kernel-bugs.kernel.org
Reporter: ekonom1@atlas.sk
Regression: No
Most important is this link
https://gitlab.gnome.org/GNOME/gparted/-/issues/311
Gparted developer says the bug is not in Gparted but in f2fs-tools
The source of the error was:
the file system was not unmounted
F2FS file system check tool not cleaning everything and requiring
additional mount and unmount
From your above supplied output fsck.f2fs reports the file system as
sudden-power-off == not cleanly unmounted. But fsck doesn't fix this
state.
lubuntu@lubuntu:~$ sudo fsck.f2fs -f /dev/sda6
...
Info: checkpoint state = 42 : crc orphan_inodes sudden-power-off
For every other file system a successful check fully cleans the file
system of all faults. But for F2FS it doesn't clear the "I need log
replaying". Only the Linux kernel f2fs code does that on mount.
This is not GParted's fault.
--
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
reply other threads:[~2026-03-14 14:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-221229-202145@https.bugzilla.kernel.org/ \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=bugzilla-daemon@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