On 03/31, beroal wrote: > On 31.03.21 04:41, Jaegeuk Kim wrote: > > Hi, > > > > On 03/27, beroal wrote: > > > Ping. > > > > > > On 20.03.21 00:46, beroal wrote: > > > > Hi. After I extended a partition containing F2FS with a recent version > > > > of Gparted, the partition no longer mounts. `mount` reports an error, > > > > but `fsck.f2fs` does not see any problem (well, except for `Invalid CP > > > > CRC offset: 0`) and does not fix the file system. > > > > > > > > ``` > > > > losetup /dev/loop0 arch-os.img > > > > mount -t f2fs -o ro /dev/loop0 /root/mnt/temp > > > > ``` > > > > > > > > ``` > > > > [ 6890.647749] F2FS-fs (loop0): Wrong valid_user_blocks: 16040048, > > > > user_block_count: 10016768 > > > > [ 6890.647808] F2FS-fs (loop0): Failed to get valid F2FS checkpoint > > > > ``` > > > > > > > > ``` > > > > losetup -d /dev/loop0 > > > > fsck.f2fs arch-os.img > > May I ask run this? > > > > # fsck.f2fs -d 3 arch-os.img? > The result is a log of size 270 MB. I'll send it privately to > [email protected] if you don't mind. It contains directory and file names.
Thanks. segment_count_main [0x 9a95 : 39573] -> 39573 * 2MB = 78GB as user space overprov_segment_count [0x 4e29 : 20009] -> 20009 * 2MB = 40GB as overprovisioned space which user can't see. But, [FSCK] valid_block_count matching with CP [Ok..] [0xf4c070] -> 0xf4c070 = 16040048 valid_block_count [0x f4c070 : 16040048] -> So, this is correct. So, I suspect overprovisioned space is wrong and guess resize.f2fs assigned a wrong value. May I ask from and to which capacities you resized? I may need to reproduce it quickly. > > > _______________________________________________ > Linux-f2fs-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
