From: Roman Mamedov <rm@romanrm.net>
To: George Duffield <forumscollective@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Understanding BTRFS storage
Date: Wed, 26 Aug 2015 16:50:24 +0500 [thread overview]
Message-ID: <20150826165024.05af044f@natsu> (raw)
In-Reply-To: <CAG__1a4T=d_O49CnOw+0gtKr56xtrmcjRcmujtUff_s_-oL0Jw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
On Wed, 26 Aug 2015 10:56:03 +0200
George Duffield <forumscollective@gmail.com> wrote:
> I'm looking to switch from a 5x3TB mdadm raid5 array to a Btrfs based
> solution that will involve duplicating a data store on a second
> machine for backup purposes (the machine is only powered up for
> backups).
What do you want to achieve by switching? As Btrfs RAID5/6 is not safe yet, do
you also plan to migrate to RAID10, losing in storage efficiency?
Why not use Btrfs in single-device mode on top of your mdadm RAID5/6? Can even
migrate without moving any data if you currently use Ext4, as it can be
converted to Btrfs in-place.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-08-26 11:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 8:56 Understanding BTRFS storage George Duffield
2015-08-26 11:41 ` Austin S Hemmelgarn
2015-08-26 11:50 ` Hugo Mills
2015-08-26 11:50 ` Roman Mamedov [this message]
2015-08-26 12:03 ` Austin S Hemmelgarn
2015-08-27 2:58 ` Duncan
2015-08-27 12:01 ` Austin S Hemmelgarn
2015-08-28 9:47 ` Duncan
2015-08-28 12:54 ` Austin S Hemmelgarn
2015-08-28 8:50 ` George Duffield
2015-08-28 9:35 ` Hugo Mills
2015-08-28 15:42 ` Chris Murphy
2015-08-28 17:11 ` Austin S Hemmelgarn
2015-08-29 8:52 ` George Duffield
2015-08-29 22:28 ` Chris Murphy
2015-09-02 5:01 ` Russell Coker
2015-08-28 9:46 ` Roman Mamedov
2015-08-26 11:50 ` Duncan
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=20150826165024.05af044f@natsu \
--to=rm@romanrm.net \
--cc=forumscollective@gmail.com \
--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