On 4/6/25 16:30, Juhyung Park wrote: > Hi all, > > I also encountered something similar a while back with resizing but > didn't report it and just manually migrated the files.
Hi Juhyung, Did you develop an individual tool to migrate specified inode to target block address? > I assisted him to ensure using the latest kernel/f2fs-tools, but his > metadata seems pretty bad right now and I suggested him to ask the > mailing list directly. 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. To Jaegeuk, any thoughts about this problem? > > The URL there should be https://arter97.com/.f2fs-20250406/fsck.log , > a little typo there. Thanks, I didn't notice this previously. > > Can we have some sort of CI/automated testing for the resizing as well? Agreed, will work on some testcases for resize.f2fs when I get some free slots. Thanks, > > Thanks. > > On Sun, Apr 6, 2025 at 1:26 AM uplinkr--- via Linux-f2fs-devel > <linux-f2fs-devel@lists.sourceforge.net> 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 >> >> >> _______________________________________________ >> 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 _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
