diff options
| author | Kent Overstreet <kent.overstreet@linux.dev> | 2023-11-13 19:57:09 -0500 |
|---|---|---|
| committer | Kent Overstreet <kent.overstreet@linux.dev> | 2024-01-01 11:47:36 -0500 |
| commit | 30418de09e6bda5478a6cfb7c1a54e128b7e2a22 (patch) | |
| tree | 88832c5ba6b4aba2339a255489fc1aecbc4b7456 | |
| parent | 0d72ab35a925d66b044cb62b709e53141c3f0143 (diff) | |
| download | lwn-30418de09e6bda5478a6cfb7c1a54e128b7e2a22.tar.gz lwn-30418de09e6bda5478a6cfb7c1a54e128b7e2a22.zip | |
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 <kent.overstreet@linux.dev>
| -rw-r--r-- | fs/bcachefs/recovery.c | 2 |
1 files changed, 2 insertions, 0 deletions
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); |