From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 00/13] btrfs-progs: check: Fix
Date: Tue, 18 Dec 2018 18:46:33 +0800 [thread overview]
Message-ID: <20181218104646.29599-1-wqu@suse.com> (raw)
This patchset can be fetched from github:
https://github.com/adam900710/btrfs-progs/tree/file_extents_fixes
The base commit is devel branch:
commit e1e7519c2d225554004b55a5c19eb196db92285a (david/devel)
Author: Qu Wenruo <wqu@suse.com>
Date: Thu Oct 25 15:35:47 2018 +0800
btrfs-progs: tests: check: Make 026-bad-dir-item-name verify if btrfs-check can also repair
Just remove the customized 'test.sh', then generic fsck test will do the
check-repair-check.
Originally for fsck-tests/001-bad-file-extent-bytenr we're going to fix
it by resetting the corrupted file extent, using the disk bytenr from
data backref.
However in real world, extent tree is the most fragile one while fs tree
is more reliable.
This means fixing using extent tree can sometimes be more dangerous, and
causing extra corruption from repair.
Further more, that test case is a big blockage for any later
modification on file extent repair code.
So the goal of this patchset is to change the repair behavior from
rebuilding file extents using data backref, to dropping invalid file
extents and modify extent tree.
Despite above change, we have some small bug fixes for:
- False alert for file extents gap
- Bad data backref -> file extent search in repair mode
The patchset is mostly from Fujitsu guys (Lu, Su Yue, Su Yanjun).
My work here is:
- Solve rebase conflicts
Mostly with DIR_ITEM hash mismatch patchset
- Commit message/comment update
Make them a little more reader friendly
- Reorder the patchset
Make small fixes first.
Lu Fengqi (2):
btrfs-progs: lowmem: fix false alert about the existence of gaps in
the check_file_extent
btrfs-progs: tests: add case for inode lose one file extent
Su Yanjun (4):
btrfs-progs: Revert "btrfs-progs: Add repair and report function for
orphan file extent."
btrfs-progs: Revert "btrfs-progs: Record orphan data extent ref to
corresponding root."
btrfs-progs: check: fix wrong @offset used in find_possible_backrefs()
btrfs-progs: check: Delete file extent item with unaligned disk bytenr
Su Yue (7):
btrfs-progs: lowmem: add argument path to punch_extent_hole()
btrfs-progs: lowmem: move nbytes check before isize check
btrfs-progs: lowmem: fix false alert if extent item has been repaired
btrfs-progs: lowmem: check unaligned disk_bytenr for extent_data
btrfs-progs: lowmem: rename delete_extent_tree_item() to delete_item()
btrfs-progs: lowmem: delete unaligned bytes extent data under repair
btrfs-progs: fsck-test: enable lowmem repair for case 001
check/main.c | 584 +++++++++++-------
check/mode-lowmem.c | 293 +++++----
check/mode-original.h | 30 +-
ctree.h | 10 +-
disk-io.c | 2 +-
.../.lowmem_repairable | 0
.../.lowmem_repairable | 0
.../default_case.img | Bin 0 -> 3072 bytes
8 files changed, 543 insertions(+), 376 deletions(-)
create mode 100644 tests/fsck-tests/001-bad-file-extent-bytenr/.lowmem_repairable
create mode 100644 tests/fsck-tests/038-missing-one-file-extent/.lowmem_repairable
create mode 100644 tests/fsck-tests/038-missing-one-file-extent/default_case.img
--
2.20.0
next reply other threads:[~2018-12-18 10:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 10:46 Qu Wenruo [this message]
2018-12-18 10:46 ` [PATCH 01/13] btrfs-progs: lowmem: fix false alert about the existence of gaps in the check_file_extent Qu Wenruo
2018-12-18 10:46 ` [PATCH 02/13] btrfs-progs: lowmem: add argument path to punch_extent_hole() Qu Wenruo
2018-12-18 10:46 ` [PATCH 03/13] btrfs-progs: lowmem: move nbytes check before isize check Qu Wenruo
2018-12-18 10:46 ` [PATCH 04/13] btrfs-progs: lowmem: fix false alert if extent item has been repaired Qu Wenruo
2018-12-18 10:46 ` [PATCH 05/13] btrfs-progs: lowmem: check unaligned disk_bytenr for extent_data Qu Wenruo
2018-12-18 10:46 ` [PATCH 06/13] btrfs-progs: lowmem: rename delete_extent_tree_item() to delete_item() Qu Wenruo
2018-12-18 10:46 ` [PATCH 07/13] btrfs-progs: lowmem: delete unaligned bytes extent data under repair Qu Wenruo
2018-12-18 10:46 ` [PATCH 08/13] btrfs-progs: Revert "btrfs-progs: Add repair and report function for orphan file extent." Qu Wenruo
2018-12-18 10:46 ` [PATCH 09/13] btrfs-progs: Revert "btrfs-progs: Record orphan data extent ref to corresponding root." Qu Wenruo
2018-12-18 10:46 ` [PATCH 10/13] btrfs-progs: check: fix wrong @offset used in find_possible_backrefs() Qu Wenruo
2018-12-18 10:46 ` [PATCH 11/13] btrfs-progs: check: Delete file extent item with unaligned disk bytenr Qu Wenruo
2018-12-18 10:46 ` [PATCH 12/13] btrfs-progs: tests: add case for inode lose one file extent Qu Wenruo
2018-12-18 10:46 ` [PATCH 13/13] btrfs-progs: fsck-test: enable lowmem repair for case 001 Qu Wenruo
2018-12-18 11:51 ` [PATCH 00/13] btrfs-progs: check: Fix Su Yue
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=20181218104646.29599-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).