e2fsck: reset lost_and_found after threads finish

This should not be kept, the reaons is similar to what
e2fsck_pass1 has done before.

Signed-off-by: Wang Shilong <wshilong@ddn.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>

diff --git a/e2fsck/pass1.c b/e2fsck/pass1.c
index 1ffa6e26ba98b946d7f96f2f8677f5c9cce3a47d..784727596f2f215d8b8501e323e89ca1c71f3be0 100644 (file)
--- a/e2fsck/pass1.c
+++ b/e2fsck/pass1.c
@@ -2992,6 +2992,11 @@ static int e2fsck_pass1_thread_join_one(e2fsck_t global_ctx, e2fsck_t thread_ctx
        /* threads might enable E2F_OPT_YES */
        global_ctx->options |= options;
        global_ctx->flags |= flags;
+       /*
+        * The l+f inode may have been cleared, so zap it now and
+        * later passes will recalculate it if necessary
+        */
+       global_ctx->lost_and_found = 0;
 
        retval = e2fsck_pass1_merge_fs(global_fs, thread_fs);
        if (retval) {