From 4ee6ff216e0a4898e55280ceb274f8f06915e2fd Mon Sep 17 00:00:00 2001 From: Wang Shilong Date: Fri, 20 Mar 2020 09:50:56 +0800 Subject: [PATCH] LU-8465 e2fsck: reset lost_and_found after threads finish This should not be kept, the reaons is similar to what e2fsck_pass1 has done before. Change-Id: Ieab9f799e159047f2d94cf5ba0568c9f146785ae Signed-off-by: Wang Shilong Reviewed-on: https://review.whamcloud.com/37999 Tested-by: jenkins Reviewed-by: Andreas Dilger Tested-by: Maloo --- e2fsck/pass1.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/e2fsck/pass1.c b/e2fsck/pass1.c index 43c80e4..b6a9da7 100644 --- a/e2fsck/pass1.c +++ b/e2fsck/pass1.c @@ -3266,6 +3266,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) { -- 1.8.3.1