From: David Sterba <dsterba@suse.cz>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: dsterba@suse.cz, Sree Harsha Totakura <sreeharsha@totakura.in>,
linux-btrfs@vger.kernel.org
Subject: Re: Confining scrub to a subvolume
Date: Tue, 5 Jan 2016 10:40:00 +0100 [thread overview]
Message-ID: <20160105094000.GP4227@twin.jikos.cz> (raw)
In-Reply-To: <1451503560.6350.3.camel@scientia.net>
On Wed, Dec 30, 2015 at 08:26:00PM +0100, Christoph Anton Mitterer wrote:
> On Wed, 2015-12-30 at 18:39 +0100, David Sterba wrote:
> > The closest would be to read the files and look for any reported
> > errors.
> Doesn't that fail for any multi-device setup, in which case btrfs reads
> the blocks only from one device, and if that verifies, doesn't check
> the other?
That's right, it's not equivalent to the scrub.
prev parent reply other threads:[~2016-01-05 9:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 0:00 Confining scrub to a subvolume Sree Harsha Totakura
2015-12-30 17:39 ` David Sterba
2015-12-30 18:26 ` Duncan
2015-12-30 19:28 ` Christoph Anton Mitterer
2015-12-30 20:57 ` Duncan
2015-12-30 21:12 ` Christoph Anton Mitterer
2016-01-04 11:01 ` Sree Harsha Totakura
2016-01-06 8:06 ` Duncan
2015-12-30 19:26 ` Christoph Anton Mitterer
2016-01-05 9:40 ` David Sterba [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=20160105094000.GP4227@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=sreeharsha@totakura.in \
/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).