From: David Sterba <dsterba@suse.cz>
To: "Lakshmipathi.G" <Lakshmipathi.G@giis.co.in>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: fsck-tests: missing csum test script
Date: Tue, 17 Jan 2017 16:06:27 +0100 [thread overview]
Message-ID: <20170117150627.GR12081@twin.jikos.cz> (raw)
In-Reply-To: <20170105192636.GA11297@fedori>
It's not clear from the test what's the purpose. There's one corrupted
csum but the whole csum tree rebuild option is used. This is a pretty
basic check that the --init-csum-tree works, so it should be mentioned
somewhere in the test script.
On Thu, Jan 05, 2017 at 08:26:36PM +0100, Lakshmipathi.G wrote:
> Signed-off-by: Lakshmipathi.G <Lakshmipathi.G@giis.co.in>
> ---
> tests/fsck-tests/027-missing-data-csum/test.sh | 39 ++++++++++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100755 tests/fsck-tests/027-missing-data-csum/test.sh
>
> diff --git a/tests/fsck-tests/027-missing-data-csum/test.sh b/tests/fsck-tests/027-missing-data-csum/test.sh
> new file mode 100755
> index 0000000..6d1dc97
> --- /dev/null
> +++ b/tests/fsck-tests/027-missing-data-csum/test.sh
> @@ -0,0 +1,39 @@
> +#!/bin/bash
> +
> +source $TOP/tests/common
> +
> +check_prereq btrfs-corrupt-block
> +check_prereq mkfs.btrfs
> +check_prereq btrfs
> +
> +setup_root_helper
> +prepare_test_dev 512M
> +
> +
> +# simulate missing csum error and repair using init-csum option
> +test_csum_corruption()
> +{
> + run_check $SUDO_HELPER $TOP/mkfs.btrfs -f $TEST_DEV
> +
> + run_check_mount_test_dev
> +
> + export DATASET_SIZE=1
> + generate_dataset small
> +
> + run_check_umount_test_dev
> +
> + # find bytenr
> + bytenr=`$SUDO_HELPER $TOP/btrfs-debug-tree $TEST_DEV | \
Please don't use btrfs-debug-tree, it's been obsoleted by the dump-tree
subcommand. And you can use the '-t csum' option to dump just the csum
tree.
> + grep "EXTENT_CSUM EXTENT_CSUM" | \
> + cut -f1 -d')' | awk '{print $6}'`
This can be simplified to one sed command.
> +
> + # corrupt csum bytenr
> + run_check $SUDO_HELPER $TOP/btrfs-corrupt-block -C $bytenr $TEST_DEV
> +
> + $SUDO_HELPER $TOP/btrfs check $TEST_DEV >& /dev/null && \
> + _fail "btrfs check failed to detect missing csum."
Here we want to capture the output from 'check' for analysis in case of
problems.
> + run_check $SUDO_HELPER $TOP/btrfs check --repair --init-csum $TEST_DEV
> + run_check $SUDO_HELPER $TOP/btrfs check $TEST_DEV
> +}
> +
> +test_csum_corruption
next prev parent reply other threads:[~2017-01-17 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 19:26 [PATCH] btrfs-progs: fsck-tests: missing csum test script Lakshmipathi.G
2017-01-17 15:06 ` David Sterba [this message]
2017-01-25 19:52 ` Lakshmipathi.G
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=20170117150627.GR12081@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=Lakshmipathi.G@giis.co.in \
--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).