From: Nikolay Borisov <nborisov@suse.com>
To: Christoph Hellwig <hch@lst.de>, fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/9] btrfs: add a helpers for read repair testing
Date: Fri, 27 May 2022 14:22:28 +0300 [thread overview]
Message-ID: <ed54f57f-4547-8b04-b59f-85c78da4b36f@suse.com> (raw)
In-Reply-To: <20220524071838.715013-2-hch@lst.de>
On 24.05.22 г. 10:18 ч., Christoph Hellwig wrote:
> Add a few helpers to consolidate code for btrfs read repair testing:
>
> - _btrfs_get_first_logical() gets the btrfs logical address for the
> first extent in a file
> - _btrfs_get_device_path and _btrfs_get_physical use the
> btrfs-map-logical tool to find the device path and physical address
> for btrfs logical address for a specific mirror
> - _btrfs_direct_read_on_mirror and _btrfs_buffered_read_on_mirror
> read the data from a specific mirror
>
> These will be used to consolidate the read repair tests and avoid
> duplication for new tests.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> common/btrfs | 75 +++++++++++++++++++++++++++++++++++++++++++++++++++
> common/config | 1 +
> 2 files changed, 76 insertions(+)
>
> diff --git a/common/btrfs b/common/btrfs
> index ac597ca4..129a83f7 100644
> --- a/common/btrfs
> +++ b/common/btrfs
> @@ -505,3 +505,78 @@ _btrfs_metadump()
> $BTRFS_IMAGE_PROG "$device" "$dumpfile"
> [ -n "$DUMP_COMPRESSOR" ] && $DUMP_COMPRESSOR -f "$dumpfile" &> /dev/null
> }
> +
> +# Return the btrfs logical address for the first block in a file
> +_btrfs_get_first_logical()
> +{
> + local file=$1
> + _require_command "$FILEFRAG_PROG" filefrag
> +
> + ${FILEFRAG_PROG} -v $SCRATCH_MNT/foobar >> $seqres.full
Likely you want to print the logical layout of the file for reference
purposes? Then use $file instead of $SCRATCH_MNT/foobar
<snip>
next prev parent reply other threads:[~2022-05-27 11:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 7:18 two more btrfs read repair tests v2 Christoph Hellwig
2022-05-24 7:18 ` [PATCH 1/9] btrfs: add a helpers for read repair testing Christoph Hellwig
2022-05-24 13:18 ` Qu Wenruo
2022-05-27 11:22 ` Nikolay Borisov [this message]
2022-05-27 13:33 ` Christoph Hellwig
2022-05-24 7:18 ` [PATCH 2/9] btrfs/140: use common read repair helpers Christoph Hellwig
2022-05-24 13:21 ` Qu Wenruo
2022-05-24 7:18 ` [PATCH 3/9] btrfs/141: " Christoph Hellwig
2022-05-24 13:21 ` Qu Wenruo
2022-05-24 7:18 ` [PATCH 4/9] btrfs/142: " Christoph Hellwig
2022-05-24 13:21 ` Qu Wenruo
2022-05-24 7:18 ` [PATCH 5/9] btrfs/143: " Christoph Hellwig
2022-05-24 13:21 ` Qu Wenruo
2022-05-24 7:18 ` [PATCH 6/9] btrfs/157: use _btrfs_get_first_logical Christoph Hellwig
2022-05-24 13:21 ` Qu Wenruo
2022-05-24 7:18 ` [PATCH 7/9] btrfs/215: " Christoph Hellwig
2022-05-24 13:21 ` Qu Wenruo
2022-05-24 7:18 ` [PATCH 8/9] btrfs: test repair with sectors corrupted in multiple mirrors Christoph Hellwig
2022-05-24 13:28 ` Qu Wenruo
2022-06-02 11:30 ` Filipe Manana
2022-06-02 12:07 ` Christoph Hellwig
2022-05-24 7:18 ` [PATCH 9/9] btrfs: test repair with corrupted sectors interleaved over " Christoph Hellwig
2022-05-24 13:30 ` Qu Wenruo
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=ed54f57f-4547-8b04-b59f-85c78da4b36f@suse.com \
--to=nborisov@suse.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--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