From: Kent Overstreet Date: Tue, 14 Nov 2023 00:57:09 +0000 (-0500) Subject: bcachefs: Flush fsck errors before running twice X-Git-Tag: microblaze-v6.10~495^2~271 X-Git-Url: http://git.monstr.eu/?a=commitdiff_plain;h=30418de09e6bda5478a6cfb7c1a54e128b7e2a22;p=linux-2.6-microblaze.git bcachefs: Flush fsck errors before running twice It's confusing if we run fsck a second time (in debug mode, to verify the second run is clean), but errors are still ratelimited from the first run. Signed-off-by: Kent Overstreet --- diff --git a/fs/bcachefs/recovery.c b/fs/bcachefs/recovery.c index 5cf7d0532002..70add8274a95 100644 --- a/fs/bcachefs/recovery.c +++ b/fs/bcachefs/recovery.c @@ -924,6 +924,8 @@ use_clean: test_bit(BCH_FS_ERRORS_FIXED, &c->flags) && !test_bit(BCH_FS_ERRORS_NOT_FIXED, &c->flags) && !test_bit(BCH_FS_ERROR, &c->flags)) { + bch2_flush_fsck_errs(c); + bch_info(c, "Fixed errors, running fsck a second time to verify fs is clean"); clear_bit(BCH_FS_ERRORS_FIXED, &c->flags);