public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: backpointer mismatch
Date: Fri, 10 Jan 2014 21:16:59 +0600	[thread overview]
Message-ID: <20140110211659.2bc9e1d7@natsu> (raw)
In-Reply-To: <pan$d701f$adb6e087$f10cdac$a6ccb243@cox.net>

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

On Fri, 10 Jan 2014 14:26:19 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:

> IOW, your backups shouldn't be btrfs, because btrfs itself is testing, 
> and any data stored on it is by definition testing-only data you don't 
> particularly care about, either because you have good tested-restorable 
> backups, or because the data really isn't that valuable to you in the 
> first place. 

On the contrary, I think a backup storage area is an excellent place to start
rolling-out btrfs from, because:

1) the snapshot capability allows to do your backups using simple full-mirror
tools such as rsync or mirrordir in incremental mode, propagating only changes
in the directory tree (and then make and keep a number of date/timed snapshots
with some automation of your own);

2) it's *backups*, by definition it's non-unique replaceable data that also
exists elsewhere (and in this case on the primary storage, that's probably
much less experimental and more redundant as well).

My primary storage is currently Ext4 and backups are all on btrfs.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-01-10 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10  3:59 backpointer mismatch Peter van Hoof
2014-01-10 14:26 ` Duncan
2014-01-10 15:16   ` Roman Mamedov [this message]
2014-01-10 15:53     ` Duncan

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=20140110211659.2bc9e1d7@natsu \
    --to=rm@romanrm.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox