From: Chris Mason <chris.mason@oracle.com>
To: "Benoît Thiébault" <benoit.thiebault@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs, broken design?
Date: Thu, 20 Jan 2011 16:20:30 -0500 [thread overview]
Message-ID: <1295558324-sup-1046@think> (raw)
In-Reply-To: <EC13E050-AA91-4DCA-B171-9CA55D537DB7@gmail.com>
Excerpts from Beno=C3=AEt Thi=C3=A9bault's message of 2011-01-20 16:06:=
21 -0500:
> Hi everyone,
>=20
> I am very interested in the features provided by btrfs.
>=20
> I know it is still under active development and thus do not consider =
using it yet "in production", but the Wikipedia page describing btrfs c=
ontains a very frightening sentence:
> "Edward Shiskin, one of the Reiser4 developers now working for Redhat=
, got asked in Q2/2010 to look more detailled into Btrfs and judged tha=
t it has a broken design. This design may lead in some cases to out of =
space problems."
>=20
> I have read the linked mail exchange in the mailing list but it is ve=
ry technical and I am not quite sure I understood everything. Could you=
please tell me if the problem has been fixed since?
There was a bug fixed as part of that discussion, and I think I also
better described the way the tree balancing works to Edward.
>=20
> Is there a planned date for the final release of btrfs?
A final release? We'll keep improving things for a long time. The
biggest missing feature today is btrfsck, which I'm working on full tim=
e
right now.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-20 21:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 21:06 btrfs, broken design? Benoît Thiébault
2011-01-20 21:20 ` Chris Mason [this message]
2011-01-21 5:25 ` Benoît Thiébault
2011-01-21 6:46 ` Chester
2011-01-21 8:11 ` Benoît Thiébault
2011-01-21 8:21 ` Hubert Kario
2011-01-21 9:54 ` version (was: btrfs, broken design?) Helmut Hullen
2011-01-21 12:21 ` Hugo Mills
2011-01-21 14:10 ` version Helmut Hullen
2011-01-21 14:32 ` version (was: btrfs, broken design?) Diego Calleja
2011-01-21 14:55 ` version Helmut Hullen
2011-01-21 15:12 ` version Hugo Mills
2011-01-21 15:19 ` version Helmut Hullen
2011-01-24 3:20 ` version Chris Samuel
2011-01-24 8:33 ` version Helmut Hullen
2011-01-24 21:14 ` version Johannes Hirte
2011-01-24 21:39 ` version Helmut Hullen
2011-01-24 22:46 ` version Chris Samuel
2011-01-25 1:03 ` version Chris Mason
2011-01-25 6:43 ` version Helmut Hullen
2011-01-25 14:37 ` version Helmut Hullen
2011-01-27 5:02 ` 2.6.38-rc2 oops's when rebalancing on different size drives (was Re: version) Chris Samuel
2011-01-27 7:45 ` version Chris Mason
2011-01-27 8:16 ` version Helmut Hullen
2011-01-27 13:28 ` version Helmut Hullen
2011-01-27 13:49 ` no space left (was: version) Helmut Hullen
2011-01-26 10:13 ` version (was: btrfs, broken design?) Erik Logtenberg
2011-01-26 14:13 ` Diego Calleja
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=1295558324-sup-1046@think \
--to=chris.mason@oracle.com \
--cc=benoit.thiebault@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).