From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Add device while rebalancing
Date: Wed, 27 Apr 2016 18:29:50 +0200 [thread overview]
Message-ID: <5720E8FE.2000407@googlemail.com> (raw)
In-Reply-To: <CAHaPQf3cR4jXKziSCqp0CnrB6oKQoO=2kywsKuo7BLqHqBjBRw@mail.gmail.com>
On 04/27/16 17:58, Juan Alberto Cirez wrote:
> Correct me if I'm wrong but the sum total of the above seems to
> suggest (at first glance) that BRTFS add several layers of complexity,
> but for little real benefit (at least in the case use of btrfs at the
> brick layer with a distributed filesystem on top)...
This may come as a surprise, but the same can be said for every other
(common) filesystem (+ device management stack) that can be used
standalone.
Jeff Darcy (of GlusterFS) just wrote a really nice blog post why
current filesystems and their historically grown requirements (mostly
as they relate to the POSIX interface standard) are in many ways
just not a good fit for scale-out/redundant storage:
http://pl.atyp.us/2016-05-updating-posix.html
Quite a few of the capabilities & features which are useful or
necessary in standalone operation (regardless of single- or multi-
device setup) are *actively unhelpful* in a distributed context, which
is why e.g. Ceph will soon do away with the on-disk filesystem for
data, and manage metadata exclusively by itself.
cheers,
Holger
next prev parent reply other threads:[~2016-04-27 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 20:36 Add device while rebalancing Juan Alberto Cirez
2016-04-23 5:38 ` Duncan
2016-04-25 11:18 ` Austin S. Hemmelgarn
2016-04-25 12:43 ` Duncan
2016-04-25 13:02 ` Austin S. Hemmelgarn
2016-04-26 10:50 ` Juan Alberto Cirez
2016-04-26 11:11 ` Austin S. Hemmelgarn
2016-04-26 11:44 ` Juan Alberto Cirez
2016-04-26 12:04 ` Austin S. Hemmelgarn
2016-04-26 12:14 ` Juan Alberto Cirez
2016-04-26 12:44 ` Austin S. Hemmelgarn
2016-04-27 0:58 ` Chris Murphy
2016-04-27 10:37 ` Duncan
2016-04-27 11:22 ` Austin S. Hemmelgarn
2016-04-27 15:58 ` Juan Alberto Cirez
2016-04-27 16:29 ` Holger Hoffstätte [this message]
2016-04-27 16:38 ` Juan Alberto Cirez
2016-04-27 16:40 ` Juan Alberto Cirez
2016-04-27 17:23 ` Holger Hoffstätte
2016-04-27 23:19 ` Chris Murphy
2016-04-28 11:21 ` 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=5720E8FE.2000407@googlemail.com \
--to=holger.hoffstaette@googlemail.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).