From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-btrfs@vger.kernel.org
Subject: Re: efficiency of btrfs cow
Date: Sun, 06 Mar 2011 11:18:55 -0500 [thread overview]
Message-ID: <4D73B3EF.6090407@interlinx.bc.ca> (raw)
In-Reply-To: <1299428248.15017.13.camel@ayu>
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
On 11-03-06 11:17 AM, Calvin Walton wrote:
>
> To add a bit to this: if you *do not* use the --inplace option on rsync,
> rsync will rewrite the entire file, instead of updating the existing
> file!
Of course. As I mentioned to Fajar previously, I am indeed using
--inplace when copying from the existing archive to the new btrfs archive.
> This of course negates some of the benefits of btrfs's COW support when
> doing incremental backups.
Absolutely.
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-03-06 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 15:46 efficiency of btrfs cow Brian J. Murrell
2011-03-06 16:02 ` Fajar A. Nugraha
2011-03-06 16:11 ` Brian J. Murrell
2011-03-06 16:17 ` Calvin Walton
2011-03-06 16:18 ` Brian J. Murrell [this message]
2011-03-06 17:22 ` Freddie Cash
2011-03-06 16:06 ` Calvin Walton
2011-03-06 16:17 ` Brian J. Murrell
2011-03-23 12:39 ` Brian J. Murrell
2011-03-23 15:53 ` Chester
2011-03-23 16:19 ` Brian J. Murrell
2011-03-23 17:36 ` Kolja Dummann
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=4D73B3EF.6090407@interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--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).