From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Martin <rc6encrypted@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Recommended why to use btrfs for production?
Date: Fri, 3 Jun 2016 08:55:18 -0400 [thread overview]
Message-ID: <aeade1fe-825c-6fc2-7f6d-85f4c5400b38@gmail.com> (raw)
In-Reply-To: <CAGQ70Yc=HHxJspMCKFBpEURRu=53pZW3k3rVDVO3QPGP_b9Tkw@mail.gmail.com>
On 2016-06-03 05:49, Martin wrote:
> Hello,
>
> We would like to use urBackup to make laptop backups, and they mention
> btrfs as an option.
>
> https://www.urbackup.org/administration_manual.html#x1-8400010.6
>
> So if we go with btrfs and we need 100TB usable space in raid6, and to
> have it replicated each night to another btrfs server for "backup" of
> the backup, how should we then install btrfs?
>
> E.g. Should we use the latest Fedora, CentOS, Ubuntu, Ubuntu LTS, or
> should we compile the kernel our self?
In general, avoid Ubuntu LTS versions when dealing with BTRFS, as well
as most enterprise distros, they all tend to back-port patches instead
of using newer kernels, which means it's functionally impossible to
provide good support for them here (because we can't know for sure what
exactly they've back-ported). I'd suggest building your own kernel if
possible, with Arch Linux being a close second (they follow upstream
very closely), followed by Fedora and non-LTS Ubuntu.
>
> And a bonus question: How stable is raid6 and detecting and replacing
> failed drives?
Do not use BTRFS raid6 mode in production, it has at least 2 known
serious bugs that may cause complete loss of the array due to a disk
failure. Both of these issues have as of yet unknown trigger
conditions, although they do seem to occur more frequently with larger
arrays.
That said, there are other options. If you have enough disks, you can
run BTRFS raid1 on top of LVM or MD RAID5 or RAID6, which provides you
with the benefits of both.
Alternatively, you could use BTRFS raid1 on top of LVM or MD RAID1,
which actually gets relatively decent performance and can provide even
better guarantees than RAID6 would (depending on how you set it up, you
can lose a lot more disks safely). If you go this way, I'd suggest
setting up disks in pairs at the lower level, and then just let BTRFS
handle spanning the data across disks (BTRFS raid1 mode keeps exactly
two copies of each block). While this is not quite as efficient as just
doing LVM based RAID6 with a traditional FS on top, it's also a lot
easier to handle reshaping the array on-line because of the device
management in BTRFS itself.
next prev parent reply other threads:[~2016-06-03 12:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 9:49 Recommended why to use btrfs for production? Martin
2016-06-03 9:53 ` Marc Haber
2016-06-03 9:57 ` Martin
2016-06-03 10:01 ` Hans van Kranenburg
2016-06-03 10:15 ` Martin
2016-06-03 12:55 ` Austin S. Hemmelgarn [this message]
2016-06-03 13:31 ` Martin
2016-06-03 13:47 ` Julian Taylor
2016-06-03 14:21 ` Austin S. Hemmelgarn
2016-06-03 14:39 ` Martin
2016-06-03 19:09 ` Christoph Anton Mitterer
2016-06-09 6:16 ` Duncan
2016-06-09 11:38 ` Austin S. Hemmelgarn
2016-06-09 17:39 ` Chris Murphy
2016-06-09 19:57 ` Duncan
2016-06-03 14:05 ` Chris Murphy
2016-06-03 14:11 ` Martin
2016-06-03 15:33 ` Austin S. Hemmelgarn
2016-06-04 0:48 ` Nicholas D Steeves
2016-06-04 1:48 ` Chris Murphy
2016-06-06 13:29 ` Austin S. Hemmelgarn
2016-06-04 1:34 ` Chris Murphy
2016-06-05 10:45 ` Mladen Milinkovic
2016-06-05 16:33 ` James Johnston
2016-06-05 18:20 ` Andrei Borzenkov
2016-06-06 1:47 ` Chris Murphy
2016-06-06 2:40 ` James Johnston
2016-06-06 13:36 ` 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=aeade1fe-825c-6fc2-7f6d-85f4c5400b38@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rc6encrypted@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.