All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benoît Thiébault" <benoit.thiebault@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs, broken design?
Date: Thu, 20 Jan 2011 22:06:21 +0100	[thread overview]
Message-ID: <EC13E050-AA91-4DCA-B171-9CA55D537DB7@gmail.com> (raw)

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?

Is there a planned date for the final release of btrfs?

Kind regards,

Ben

             reply	other threads:[~2011-01-20 21:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 21:06 Benoît Thiébault [this message]
2011-01-20 21:20 ` btrfs, broken design? Chris Mason
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=EC13E050-AA91-4DCA-B171-9CA55D537DB7@gmail.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.