From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: chunk and dev-extent related error handler enhancement
Date: Mon, 9 Jul 2018 14:42:01 +0800 [thread overview]
Message-ID: <20180709064203.32409-1-wqu@suse.com> (raw)
Can be fetched with all existing tree-checker/bg<->chunk error detector
from github:
https://github.com/adam900710/linux/tree/tree_checker_enhance
Still some fuzzed images reported from Xu Wen.
This time, 2 can be fixed by chunk <-> dev extent mapping verification.
One BUG_ON() can be removed.
The remaining 2 images are all mostly about extent tree corruption,
which is not as easy to detect, since extent tree has way more complex
reference relationship.
At least, fix what we can first.
And for chunk <-> dev extent mapping verification, it will trigger
read on the whole device tree, to iterate through all DEV_EXTENT items.
This will introduce an extra overhead on mount.
However since device tree is pretty small (the same level as chunk tree),
and according to previous analyse on mount time, chunk tree iteration is
only a pretty small fraction of the whole mount time (less than 5%), it
shouldn't bring obvious impact to users.
Qu Wenruo (2):
btrfs: Introduce mount time chunk <-> dev extent mapping check
btrfs: Exit gracefully when failed to add chunk map
fs/btrfs/disk-io.c | 7 ++
fs/btrfs/volumes.c | 181 ++++++++++++++++++++++++++++++++++++++++++++-
fs/btrfs/volumes.h | 2 +
3 files changed, 188 insertions(+), 2 deletions(-)
--
2.18.0
next reply other threads:[~2018-07-09 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 6:42 Qu Wenruo [this message]
2018-07-09 6:42 ` [PATCH 1/2] btrfs: Introduce mount time chunk <-> dev extent mapping check Qu Wenruo
2018-07-16 13:06 ` David Sterba
2018-07-31 7:45 ` Qu Wenruo
2018-07-09 6:42 ` [PATCH 2/2] btrfs: Exit gracefully when failed to add chunk map Qu Wenruo
2018-07-16 13:08 ` [PATCH 0/2] btrfs: chunk and dev-extent related error handler enhancement 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=20180709064203.32409-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).