From: uplinkr--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Resize metadata corruption
Date: Thu, 10 Apr 2025 09:19:28 +0300 [thread overview]
Message-ID: <80e1ae8eddff0536f09ca07e802fb983@airmail.cc> (raw)
In-Reply-To: <6e929f78-ab82-434b-a553-6e56d38fcfcc@kernel.org>
On 2025-04-10 08:52, Chao Yu wrote:
> I checked the log, I guess it actually seems pretty bad... I guess we
> need to find out those file which has not been migrated correctly, and
> try to correct them, may be w/ a new tool.
Hello,
The issue is the corrupt partition in question contains a lot of
unbackupped, valuable data for me. I wasn't aware or informed of the
potential issues resizing on F2FS has (the ArchWiki listed none) and as
such recovery of this partition is a lifeline for me.
Could you please write this tool or a patch that I can try in fsck?
Thanks.
_______________________________________________
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:[~2025-04-10 6:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-06 8:04 [f2fs-dev] Resize metadata corruption uplinkr--- via Linux-f2fs-devel
2025-04-06 8:30 ` Juhyung Park
2025-04-08 5:33 ` uplinkr--- via Linux-f2fs-devel
2025-04-10 5:52 ` Chao Yu via Linux-f2fs-devel
2025-04-10 5:57 ` Juhyung Park
2025-04-10 7:00 ` Chao Yu via Linux-f2fs-devel
2025-04-10 7:08 ` Juhyung Park
2025-04-10 7:34 ` Chao Yu via Linux-f2fs-devel
2025-04-10 6:19 ` uplinkr--- via Linux-f2fs-devel [this message]
2025-04-10 7:17 ` Chao Yu via Linux-f2fs-devel
2025-04-10 7:31 ` uplinkr--- via Linux-f2fs-devel
2025-04-11 5:26 ` Juhyung Park
2025-04-11 7:05 ` Chao Yu via Linux-f2fs-devel
2025-04-11 15:49 ` uplinkr--- via Linux-f2fs-devel
2025-04-14 2:51 ` Chao Yu via Linux-f2fs-devel
2025-04-08 5:43 ` Chao Yu via Linux-f2fs-devel
2025-04-08 6:10 ` uplinkr--- via Linux-f2fs-devel
2025-04-08 6:18 ` Chao Yu via Linux-f2fs-devel
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=80e1ae8eddff0536f09ca07e802fb983@airmail.cc \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=uplinkr@airmail.cc \
/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.