From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH] btrfs-progs: Continue checking even we found something wrong in free space cache
Date: Tue, 4 Sep 2018 20:41:28 +0800 [thread overview]
Message-ID: <20180904124128.22367-1-wqu@suse.com> (raw)
No need to abort checking, especially for RO check free space cache is
meaningless, the errors in fs/extent tree is more interesting for
developers.
So continue checking even something in free space cache is wrong.
Reported-by: Etienne Champetier <champetier.etienne@gmail.com>
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
check/main.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/check/main.c b/check/main.c
index b361cd7e26a0..4f720163221e 100644
--- a/check/main.c
+++ b/check/main.c
@@ -9885,7 +9885,6 @@ int cmd_check(int argc, char **argv)
error("errors found in free space tree");
else
error("errors found in free space cache");
- goto out;
}
/*
--
2.18.0
next reply other threads:[~2018-09-04 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 12:41 Qu Wenruo [this message]
2018-09-11 14:48 ` [PATCH] btrfs-progs: Continue checking even we found something wrong in free space cache David Sterba
2018-09-11 23:43 ` Qu Wenruo
2018-09-14 14:32 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180904124128.22367-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).