From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs send and an existing backup
Date: Thu, 20 Nov 2014 14:10:13 +0000 (UTC) [thread overview]
Message-ID: <pan$483ea$3a099fee$7e09d57b$ed49879a@cox.net> (raw)
In-Reply-To: m4kpm0$r52$1@ger.gmane.org
Bardur Arantsson posted on Thu, 20 Nov 2014 14:17:52 +0100 as excerpted:
> If you have no other backups, I would really recommend that you *don't*
> use btrfs for your backup, or at least have a *third* backup which isn't
> on btrfs -- there are *still* problems with btrfs that can potentially
> wreck your backup filesystem. (Although it's obviously less likely if
> the external HDD will only be connected occasionally.)
>
> Don't get me wrong, btrfs is becoming more and more stable, but I
> wouldn't trust it with my *only* backup, especially if also running
> btrfs on the backed-up filesystem.
This.
My working versions and first backups are btrfs. My secondary backups
are reiserfs (my old filesystem of choice, which has been very reliable
for me), just in case both the btrfs versions bite the dust due to a bug
in btrfs itself.
--
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
next prev parent reply other threads:[~2014-11-20 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 15:58 btrfs send and an existing backup Jakob Schürz
2014-11-20 12:05 ` Marc Joliet
2014-11-20 13:17 ` Bardur Arantsson
2014-11-20 14:10 ` Duncan [this message]
2014-11-21 12:51 ` Austin S Hemmelgarn
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$483ea$3a099fee$7e09d57b$ed49879a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox