From: Roman Mamedov <rm@romanrm.net>
To: Wols Lists <antlists@youngman.org.uk>
Cc: Alex <mysqlstudent@gmail.com>, Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Recommendations for RAID setup needed
Date: Tue, 15 Sep 2015 23:57:31 +0500 [thread overview]
Message-ID: <20150915235731.5fcc5f79@natsu> (raw)
In-Reply-To: <55F85E9F.1070100@youngman.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
On Tue, 15 Sep 2015 19:08:31 +0100
Wols Lists <antlists@youngman.org.uk> 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.
However its RAID5/6 is not ready yet and even RAID1/10 lack some important
features compared to mdadm, not to mention performance optimizations.
On the other hand I have a great success running Btrfs without utilizing its
own RAID features, but as a regular filesystem on top of MD RAID5/6.
> 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.
And this is just an absolute deranged baseless FUD today, or maybe something
that might have been true about 5 years ago -- eons in Btrfs development.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-09-15 18:57 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 [this message]
2015-09-22 4:18 ` David C. Rankin
2015-09-22 4:16 ` David C. Rankin
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=20150915235731.5fcc5f79@natsu \
--to=rm@romanrm.net \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mysqlstudent@gmail.com \
/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.