Currently, directory should not have any extent cache entry.
Otherwise, fsck.f2fs will trigger a false-alarmed report.

Signed-off-by: Jaegeuk Kim <jaeg...@kernel.org>
---
 mkfs/f2fs_format.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/mkfs/f2fs_format.c b/mkfs/f2fs_format.c
index fff74a9..98a6bce 100644
--- a/mkfs/f2fs_format.c
+++ b/mkfs/f2fs_format.c
@@ -769,8 +769,8 @@ static int f2fs_write_root_inode(void)
        raw_node->i.i_addr[0] = cpu_to_le32(data_blk_nor);
 
        raw_node->i.i_ext.fofs = 0;
-       raw_node->i.i_ext.blk_addr = cpu_to_le32(data_blk_nor);
-       raw_node->i.i_ext.len = cpu_to_le32(1);
+       raw_node->i.i_ext.blk_addr = 0;
+       raw_node->i.i_ext.len = 0;
 
        main_area_node_seg_blk_offset = get_sb(main_blkaddr);
        main_area_node_seg_blk_offset += config.cur_seg[CURSEG_HOT_NODE] *
-- 
2.5.4 (Apple Git-61)


------------------------------------------------------------------------------
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Reply via email to