From: Roman Mamedov <rm@romanrm.net>
To: Diego Torres <diego.torres@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs stability
Date: Fri, 27 May 2016 10:14:57 +0500 [thread overview]
Message-ID: <20160527101457.2c560376@natsu> (raw)
In-Reply-To: <CAKg6aQzTx7NLjC6gZxKUKkuACo313N3ZqxQ0SXO4WXEwGPFNkg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
On Fri, 27 May 2016 00:42:07 +0200
Diego Torres <diego.torres@gmail.com> wrote:
> Btrfs is the only fs that can add drives one by one to an existing raid
> setup, and use the new space inmediately, without replacing all the drives.
Ext4, XFS, JFS or pretty much any FS which can be resized upwards can also do
that, when placed on top of mdadm RAID5/6. It's not like you are absolutely
locked in to using Btrfs if you need that particular feature.
"Some of us" also prefer to use Btrfs on top of mdadm RAID, to benefit both
from Btrfs' advanced features such as snapshots, compression and checksum
verification (but not corruption resilience in this case), and from mdadm's
mature, well-tested and performant RAID implementations.
--
With respect,
Roman
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-05-27 5:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 22:42 btrfs stability Diego Torres
2016-05-27 1:28 ` btrfs [raid56] stability Duncan
2016-05-27 5:14 ` Roman Mamedov [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-25 20:05 btrfs stability Andrew McNabb
2013-01-25 20:37 ` Josef Bacik
2013-01-25 21:22 ` Andrew McNabb
2013-01-25 20:53 ` Josef Bacik
2013-01-25 21:39 ` Andrew McNabb
2013-01-26 20:27 ` Andrew McNabb
2013-01-28 14:17 ` Josef Bacik
2013-01-28 15:10 ` Josef Bacik
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=20160527101457.2c560376@natsu \
--to=rm@romanrm.net \
--cc=diego.torres@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;
as well as URLs for NNTP newsgroup(s).