From: Vladimir Panteleev <git@vladimir.panteleev.md>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: scrub: add start/end position for scrub
Date: Wed, 4 Dec 2019 22:11:22 +0000 [thread overview]
Message-ID: <CAHhfkvzvtDcg7Jv=E3fm4mWnHT80VkGxwEX=6akbebA_Zno3kw@mail.gmail.com> (raw)
In-Reply-To: <20191202034420.4634-2-ce3g8jdj@umail.furryterror.org>
Thank you for this! I've put together a script which uses the added
switches to rescan observed errors in dmesg:
https://gist.github.com/CyberShadow/648a040103fb08738783b6435da376fe
Though, the approach described in the cover letter is probably a
better idea than what this script does.
On Mon, 2 Dec 2019 at 03:47, Zygo Blaxell
<ce3g8jdj@umail.furryterror.org> wrote:
> +-s <start_pos>::::
> +set start position by logical address (btrfs extent bytenr, default 0)
> +-e <end_pos>::::
> +set end position by logical address (btrfs extent bytenr, default end of filesystem)
As mentioned on IRC, I found it confusing that these use the term
"logical addresses" to describe what the dmesg errors refer to as
"physical" addresses.
prev parent reply other threads:[~2019-12-04 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 3:44 [RFC PATCH 0/1] btrfs-progs: scrub: add start/end position for scrub Zygo Blaxell
2019-12-02 3:44 ` [PATCH] " Zygo Blaxell
2019-12-04 22:11 ` Vladimir Panteleev [this message]
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='CAHhfkvzvtDcg7Jv=E3fm4mWnHT80VkGxwEX=6akbebA_Zno3kw@mail.gmail.com' \
--to=git@vladimir.panteleev.md \
--cc=ce3g8jdj@umail.furryterror.org \
--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).