From: Christoph Hellwig <hch@lst.de>
To: Anand Jain <anand.jain@oracle.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Christoph Hellwig <hch@lst.de>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs: test repair with corrupted sectors interleaved over multiple mirrors
Date: Sun, 22 May 2022 15:00:29 +0200 [thread overview]
Message-ID: <20220522130029.GA25364@lst.de> (raw)
In-Reply-To: <1fc36e3f-8fa9-2bfb-ede1-d4f852bcb8cf@oracle.com>
On Sun, May 22, 2022 at 06:26:26PM +0530, Anand Jain wrote:
> Agreed this method is unreliable. But there is no other choice.
> Unless we integrated [1] patch in the ML.
>
> [1] btrfs: introduce new read_policy device
>
> [1] is more reliable. You can set which mirrored device to read.
I actually thought about something like this as the reliable way
to hit a mirror. Besides testing I could also thing of some other
use cases for it where you want to avoid a mirror by default for some
reason (e.g. because it is network attached store while the other
one is local).
prev parent reply other threads:[~2022-05-22 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 16:47 two more btrfs read repair tests Christoph Hellwig
2022-05-20 16:47 ` [PATCH 1/2] btrfs: test repair with sectors corrupted in multiple mirrors Christoph Hellwig
2022-05-21 2:02 ` Zorro Lang
2022-05-22 1:13 ` Anand Jain
2022-05-20 16:47 ` [PATCH 2/2] btrfs: test repair with corrupted sectors interleaved over " Christoph Hellwig
2022-05-22 1:13 ` Anand Jain
2022-05-22 6:31 ` Qu Wenruo
2022-05-22 12:56 ` Anand Jain
2022-05-22 13:00 ` Christoph Hellwig [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=20220522130029.GA25364@lst.de \
--to=hch@lst.de \
--cc=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.