Any comment?
At 11/22/2016 04:38 PM, Qu Wenruo wrote:
Despite the scrub test cases in fstests, there is not even one test case
which really checked if scrub can recover data.
In fact, btrfs scrub for RAID56 will even corrupt correct data stripes.
So let's start from the needed facilities and check scrub starting from RAID1.
The main reason the patchset is RFC, is the method I take to corrupt/verify
btrfs data.
unlike other stable fs, like ext* or xfs, which has good tool to
manipulate the fs.
There used to be btrfs-corrupt-block, but it gets fewer and fewer
update, no man page nor installed by default.
Here I take the method I normally do in my scripts: use btrfs-dump-tree
(btrfs inspect-internal dump-tree) and use bash to corrupt btrfs
pinpointly.
It works quite fine for several different mount options which affects
how data lies on-disk.
But the problem is also obvious, bash script is super hard to maintain,
and there is no promise that btrfs-dump-tree output won't change.
Such change will be destructive.
But IMHO it's still worthy, or btrfs scrub may break at any time.
Qu Wenruo (3):
fstests: common: rename _require_btrfs to _require_btrfs_subcommand
fstests: common/ondisk.btrfs: Introduce function to get btrfs ondisk
info
Especially for fstests guys, is this OK to use complex bash scripts to
extract needed data for btrfs?
Or should we just put things into btrfs-progs (and wait for some time,
leaving btrfs raid56 corrupted)
Thanks,
Qu
fstests: btrfs: Add new test case to check scrub recovery and report
common/ondisk.btrfs | 113 ++++++++++++++++++++++++++
common/rc | 2 +-
tests/btrfs/004 | 2 +-
tests/btrfs/048 | 2 +-
tests/btrfs/059 | 2 +-
tests/btrfs/131 | 2 +-
tests/btrfs/132 | 229 ++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/132.out | 111 +++++++++++++++++++++++++
tests/btrfs/group | 2 +
9 files changed, 460 insertions(+), 5 deletions(-)
create mode 100644 common/ondisk.btrfs
create mode 100755 tests/btrfs/132
create mode 100644 tests/btrfs/132.out
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
