From e325c74bb8af9efa150cb16429a94f291209604f Mon Sep 17 00:00:00 2001 From: Goldwyn Rodrigues Date: Tue, 20 Dec 2016 06:08:54 -0600 Subject: btrfs-progs: check: get the highest inode for lost+found root->highest_inode is not accurate at the time of creating a lost+found and it fails because the highest_inode+1 is already present. This could be because of fixes after highest_inode is set. Instead, search for the highest inode in the tree and use it for lost+found. This makes root->highest_inode unnecessary and hence deleted. Signed-off-by: Goldwyn Rodrigues Reviewed-by: Qu Wenruo Signed-off-by: David Sterba --- disk-io.c | 1 - 1 file changed, 1 deletion(-) (limited to 'disk-io.c') diff --git a/disk-io.c b/disk-io.c index 9140a81b..2a94d4fc 100644 --- a/disk-io.c +++ b/disk-io.c @@ -494,7 +494,6 @@ void btrfs_setup_root(u32 nodesize, u32 leafsize, u32 sectorsize, root->fs_info = fs_info; root->objectid = objectid; root->last_trans = 0; - root->highest_inode = 0; root->last_inode_alloc = 0; INIT_LIST_HEAD(&root->dirty_list); -- cgit v1.2.3