f2fs: avoid to calculate incorrect max orphan number
Subsystems (2)
PATCH 1/1 f2fs: avoid to calculate incorrect max orphan number
Because we will write node summaries when do_checkpoint with umount flag, our number of max orphan blocks should minus NR_CURSEG_NODE_TYPE additional.
Signed-off-by Chao Yu <[email protected]>
Signed-off-by Shu Tan <[email protected]>
--- fs/f2fs/checkpoint.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
fs/f2fs/checkpoint.c +4 -3
@@ -190,12 +190,13 @@ int acquire_orphan_inode(struct f2fs_sb_info *sbi)int err =0 ;/* -* considering 512 blocks in a segment 5 blocks are needed for cp +* considering 512 blocks in a segment 8 blocks are needed for cp * and log segment summaries. Remaining blocks are used to keep * orphan entries with the limitation one reserved segment -* for cp pack we can have max 1020*507 orphan entries +* for cp pack we can have max 1020*504 orphan entries */ - max_orphans = (sbi->blocks_per_seg -5 ) *F2FS_ORPHANS_PER_BLOCK ; + max_orphans = (sbi->blocks_per_seg -2 -NR_CURSEG_TYPE ) + *F2FS_ORPHANS_PER_BLOCK ;mutex_lock (&sbi->orphan_inode_mutex);if (sbi->n_orphans >= max_orphans) err = -ENOSPC ;
Signature · 9 lines
1.7.9.5 ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk