From bff1280c5a380dd1f89926f1abe76e3cc657f676 Mon Sep 17 00:00:00 2001 From: Wang Shilong Date: Fri, 20 Mar 2020 09:50:56 +0800 Subject: [PATCH] e2fsck: reset lost_and_found after threads finish This should not be kept, the reaons is similar to what e2fsck_pass1 has done before. E2fsprogs-commit: 10abbf8fd534d61c40fbf9699bf605ac6456b2e2 Change-Id: I0e431be7619720e31927ab1df7034aee1e3eb747 Signed-off-by: Wang Shilong Reviewed-by: Andreas Dilger Signed-off-by: Theodore Ts'o --- e2fsck/pass1.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/e2fsck/pass1.c b/e2fsck/pass1.c index d31c7f0..e47d42f 100644 --- a/e2fsck/pass1.c +++ b/e2fsck/pass1.c @@ -3115,6 +3115,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