Re: btrfs, broken design?
[Posted February 23, 2011 by corbet]
| From: |
| Chris Mason <chris.mason-AT-oracle.com> |
| To: |
| Benoît Thiébault <benoit.thiebault-AT-gmail.com> |
| Subject: |
| Re: btrfs, broken design? |
| Date: |
| Thu, 20 Jan 2011 16:20:30 -0500 |
| Message-ID: |
| <1295558324-sup-1046@think> |
| Cc: |
| linux-btrfs <linux-btrfs-AT-vger.kernel.org> |
| Archive-link: |
| Article, Thread
|
Excerpts from Benoît Thiébault's message of 2011-01-20 16:06:21 -0500:
> Hi everyone,
>
> I am very interested in the features provided by btrfs.
>
> I know it is still under active development and thus do not consider using it yet "in
production", but the Wikipedia page describing btrfs contains 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 that it has a broken design. This design may lead in some
cases to out of space problems."
>
> I have read the linked mail exchange in the mailing list but it is very 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.
>
> 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 time
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
(
Log in to post comments)