From: Sree Harsha Totakura <sreeharsha@totakura.in>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: Confining scrub to a subvolume
Date: Mon, 4 Jan 2016 12:01:58 +0100 [thread overview]
Message-ID: <568A5126.20801@totakura.in> (raw)
In-Reply-To: <pan$88aff$ee7e2e75$cb54e003$bedb8f3a@cox.net>
On 12/30/2015 07:26 PM, Duncan wrote:
> David Sterba posted on Wed, 30 Dec 2015 18:39:49 +0100 as excerpted:
>
>> On Wed, Dec 30, 2015 at 01:00:34AM +0100, Sree Harsha Totakura wrote:
>>> Is it possible to confine scrubbing to a subvolume instead of the whole
>>> file system?
>>
>> No. Srub reads the blocks from devices (without knowing which files own
>> them) and compares them to the stored checksums.
>
> Of course if like me you prefer not to have all your data eggs in one
> filesystem basket and have used partitions (or LVM) and multiple
> independent btrfs, in which case you scrub the filesystem you want, and
> don't worry about the others. =:^)
I considered it, but after reading somewhere (couldn't find the source)
that having a single btrfs could be beneficial, I decided not to.
Clearly, it doesn't seem to be true in this case.
Thank you all for your comments and suggestions. I will be using
different btrfs file systems based.
Regards,
Sree Harsha Totakura
next prev parent reply other threads:[~2016-01-04 14:37 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 [this message]
2016-01-06 8:06 ` Duncan
2015-12-30 19:26 ` Christoph Anton Mitterer
2016-01-05 9:40 ` David Sterba
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=568A5126.20801@totakura.in \
--to=sreeharsha@totakura.in \
--cc=1i5t5.duncan@cox.net \
--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 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.