From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: uplinkr@airmail.cc
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Resize metadata corruption
Date: Tue, 8 Apr 2025 14:18:26 +0800 [thread overview]
Message-ID: <608f23ce-56ef-4faf-bee1-3aa89786ed41@kernel.org> (raw)
In-Reply-To: <f192a85424972b524c1f49fa28a7bd8c@airmail.cc>
On 4/8/25 14:10, uplinkr@airmail.cc wrote:
> Hello,
>
> I made a typo in the URL earlier. It should be https://arter97.com/.f2fs-20250406/fsck.log . Could you try it, please?
Ah, alright.
Now, I can access it, thank you. Let me check the details in the log.
Thanks,
>
> Thanks.
>
> On 2025-04-08 08:43, Chao Yu wrote:
>> On 4/6/25 16:04, uplinkr--- via Linux-f2fs-devel wrote:
>>> Hello everyone,
>>>
>>> I am having trouble with F2FS. Specifically, I believe metadata got corrupted when I resized it. I have a 512 GB drive. My F2FS partition was approximately located on 369-497 GB (128 GB size). Using
>>> GParted, I resized it to 0.5-497 GB. While the partition resizing went through successfully, filesystem resizing initially failed with "Mount unclean image to replay log". I have done that and retried
>>> resizing.
>>>
>>> Afterwards, however, fsck started giving out a lot of errors, at one point it asked if I wished to restore lost data, which I agreed to. Logs specified a lot of my files (which I could tell by
>>> filenames) and mid-way through the process, it segfaulted. Now, when I run fsck, no files are asked to be restored, and it completes successfully. However, when I attempt to mount it, I get an error
>>> saying "Structure needs cleaning".
>>>
>>> Could someone help me restore my metadata (at least, long enough to extract my files)? Thanks.
>>>
>>> dmesg logs:
>>>
>>> [ 96.184127] F2FS-fs (nvme0n1p5): Mismatch valid blocks 769 vs. 68
>>> [ 96.188050] F2FS-fs (nvme0n1p5): Failed to initialize F2FS segment manager (-117)
>>>
>>> fsck.f2fs --dry-run -d 3 logs: https://arter.com/.f2fs-20250406/fsck.log
>>
>> Hello,
>>
>> Could you please upload fsck.log in bugzilla.kernel.org, or somewhere else?
>> I can not download it from above link address, sorry.
>>
>> Thanks,
>>
>>>
>>>
>>> _______________________________________________
>>> Linux-f2fs-devel mailing list
>>> Linux-f2fs-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2025-04-08 6:18 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
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 [this message]
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=608f23ce-56ef-4faf-bee1-3aa89786ed41@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@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.