All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: backpointer mismatch
Date: Fri, 10 Jan 2014 15:53:19 +0000 (UTC)	[thread overview]
Message-ID: <pan$3cf85$2453ae59$210fcea3$d7c39e55@cox.net> (raw)
In-Reply-To: 20140110211659.2bc9e1d7@natsu

Roman Mamedov posted on Fri, 10 Jan 2014 21:16:59 +0600 as excerpted:

> 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 

Point agreed. =:^)

> 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.

But what happens if you actually /need/ those backups, and in going to 
use them, you find they're bugged due to some as yet unfixed bug in still 
under development btrfs?

To me, the /point/ of backups is reliability.  I need to *KNOW* they're 
reliable, and btrfs simply isn't intended or claimed to provide that 
guaranteed stable reliability yet.

While admittedly a lot of people are now using btrfs without issue, and 
I'm using it here myself as my primary/working copy as well as first 
level backup (with off-btrfs backups to my first-level btrfs backups), I 
simply couldn't rest well if I were using it for (all level) backups, 
because it simply doesn't provide the proven over years level of 
stability and reliability that for me is the whole /point/ of backups 
(otherwise, why bother?), yet.

Never-the-less, if you're comfortable with that level of additional risk 
in your backups, it's your system and your data at risk, so more power to 
you! =:^)

But IMO, /recommending/ btrfs for backups at this point (regardless of 
what I was or was not doing myself, accepting the brown-bag should my 
decision for my own data turn out to have been a bad one) is nothing 
other than irresponsible, and as such I could never do it.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


      reply	other threads:[~2014-01-10 15:53 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
2014-01-10 15:53     ` Duncan [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='pan$3cf85$2453ae59$210fcea3$d7c39e55@cox.net' \
    --to=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.