All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David C. Rankin" <drankinatty@suddenlinkmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Recommendations for RAID setup needed
Date: Mon, 21 Sep 2015 23:16:26 -0500	[thread overview]
Message-ID: <5600D61A.6000908@suddenlinkmail.com> (raw)
In-Reply-To: <55F85E9F.1070100@youngman.org.uk>

On 9/15/2015 1:08 PM, Wols Lists wrote:
> Throwing something completely different into the mix, how about
> considering btrfs? It's not 100% solid yet, so you need to be careful
> with it, but if you back up with rsync and the "in place" option, it'll
> give you full backups for the cost of incremental.
>
> What you MUST do is KEEP AN EYE ON DISK SPACE! The main failure mode for
> btrfs I'm aware of, is that a disk full can cause a fatal error. As in
> "I've just trashed the disk - it's 'format c:' time". So if you hit 80%
> or so, alarm bells should be ringing. Very loud.

This is the exact reason NOT to use btrfs at the moment. The issue is 
with the 'snap shotting' feature which can quietly fill your disk with 
snap shots to the point of space exhaustion that has resulted in the 
complete loss of information in a number of instances.

Why would you recommend a filesystem when "It's not 100% solid yet" to 
someone looking for enhanced data integrity?

Your warning is well taken, and while btrfs is getting better all the 
time, for a raid install where the object is to eliminate (or greatly 
lessen) the chance of data loss, stick with a tried and true filesystem 
unless you want to become an unwitting beta-tester with your data on the 
line...

-- 
David C. Rankin, J.D.,P.E.

  parent reply	other threads:[~2015-09-22  4:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 17:39 Recommendations for RAID setup needed Alex
2015-09-15 18:08 ` Wols Lists
2015-09-15 18:44   ` Alex
2015-09-16  2:12     ` Adam Goryachev
2015-09-16 10:03       ` Jens-U. Mozdzen
2015-09-16 15:53       ` Alex
2015-09-18 11:25         ` Michael Tokarev
2015-09-18 12:55           ` Alex
2015-09-15 18:57   ` Roman Mamedov
2015-09-22  4:18     ` David C. Rankin
2015-09-22  4:16   ` David C. Rankin [this message]
2015-09-22  5:03     ` Roman Mamedov

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=5600D61A.6000908@suddenlinkmail.com \
    --to=drankinatty@suddenlinkmail.com \
    --cc=linux-raid@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.