Linux-BTRFS Archive on
 help / color / Atom feed
From: Vladimir Panteleev <>
To: Zygo Blaxell <>
Cc: Btrfs BTRFS <>
Subject: Re: [PATCH] btrfs-progs: scrub: add start/end position for scrub
Date: Wed, 4 Dec 2019 22:11:22 +0000
Message-ID: <> (raw)
In-Reply-To: <>

Thank you for this! I've put together a script which uses the added
switches to rescan observed errors in dmesg:

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
<> 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.

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02  3:44 [RFC PATCH 0/1] " Zygo Blaxell
2019-12-02  3:44 ` [PATCH] " Zygo Blaxell
2019-12-04 22:11   ` Vladimir Panteleev [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-BTRFS Archive on

Archives are clonable:
	git clone --mirror linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ \
	public-inbox-index linux-btrfs

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone