diff options
author | Lihong Kou <koulihong@huawei.com> | 2019-08-05 15:26:21 +0800 |
---|---|---|
committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2019-08-27 14:51:05 -0700 |
commit | 66087b1521047a55869c9cece55592edd594cd92 (patch) | |
tree | 68462f5a3d02d6f21cc0cfaea97e6aebd945a2d5 | |
parent | 121f29b7b9f2bb71ba73ef10819ad6de8ba70eab (diff) | |
download | f2fs-tools-66087b1521047a55869c9cece55592edd594cd92.tar.gz |
fsck.f2fs: fix the bug in reserve_new_block
if we new node block in fsck flow, we need to update
the valid_node_cnt at the same time.
Signed-off-by: Lihong Kou <koulihong@huawei.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
-rw-r--r-- | fsck/segment.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/fsck/segment.c b/fsck/segment.c index 1b58b70..367865a 100644 --- a/fsck/segment.c +++ b/fsck/segment.c @@ -58,8 +58,11 @@ int reserve_new_block(struct f2fs_sb_info *sbi, block_t *to, if (old_blkaddr == NULL_ADDR) { sbi->total_valid_block_count++; - if (c.func == FSCK) + if (c.func == FSCK) { fsck->chk.valid_blk_cnt++; + if (IS_NODESEG(type)) + fsck->chk.valid_node_cnt++; + } } se->dirty = 1; |