resize.f2fs: fix wrong ovp calculation
authorJaegeuk Kim <jaegeuk@kernel.org>
Fri, 2 Apr 2021 03:13:55 +0000 (20:13 -0700)
committerJaegeuk Kim <jaegeuk@kernel.org>
Fri, 2 Apr 2021 03:19:10 +0000 (20:19 -0700)
commitf056fbeff08d30a6d9acdb9e06704461ceee3500
tree638de96bff9013be60c9c1effb279bb00b093ec2
parent80dba0f97549d5fc45ea1530a02da51c5908082c
resize.f2fs: fix wrong ovp calculation

beroal reported a mount failure due to broken valid_user_blocks.
[ 6890.647749] F2FS-fs (loop0): Wrong valid_user_blocks: 16040048,
user_block_count: 10016768

From fsck,

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.

It turns out resize.f2fs gave very large and wrong overprovisioning space
result in shortage of user blocks. The root cause was f2fs_get_usable_segments()
didn't consider resize case which needs segment_count_main from new superblock.

Fixes: f8410857b7a8 ("f2fs-tools: zns zone-capacity support")
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
lib/libf2fs_zoned.c