[f2fs-dev] Resize metadata corruption

2025-04-06 Thread uplinkr--- via Linux-f2fs-devel
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

Re: [f2fs-dev] Resize metadata corruption

2025-04-07 Thread uplinkr--- via Linux-f2fs-devel
Hello, I made a typo in the URL earlier. It should be https://arter97.com/.f2fs-20250406/fsck.log . Could you try it, please? 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

Re: [f2fs-dev] Resize metadata corruption

2025-04-07 Thread uplinkr--- via Linux-f2fs-devel
t directly. The URL there should be https://arter97.com/.f2fs-20250406/fsck.log , a little typo there. Can we have some sort of CI/automated testing for the resizing as well? Thanks. On Sun, Apr 6, 2025 at 1:26 AM uplinkr--- via Linux-f2fs-devel wrote: Hello everyone, I am having trouble

Re: [f2fs-dev] Resize metadata corruption

2025-04-10 Thread uplinkr--- via Linux-f2fs-devel
On 2025-04-10 10:17, Chao Yu wrote: But still I didn't get why we can run into this situation, since as you said, resize went through successfully. Could you please provide more details about process of resize? Parameters for resize? Logs you kept during resize? etc. Hello, I'm afraid I don't

Re: [f2fs-dev] Resize metadata corruption

2025-04-09 Thread uplinkr--- via Linux-f2fs-devel
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 u

Re: [f2fs-dev] Resize metadata corruption

2025-04-11 Thread uplinkr--- via Linux-f2fs-devel
Hello everyone, I'm sorry to not have anything constructive to add, but I'm about as flabbergasted as I could be. I retraced all my steps (exactly as I went through with them before!) and was unable to replicate the corruption. On the contrary, the filesystem grew completely as expected. Aft