linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chester <somethingsome2000@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs, broken design?
Date: Fri, 21 Jan 2011 00:46:44 -0600	[thread overview]
Message-ID: <AANLkTikGPRrdaj2SO5ZwjD8pZEVNj4pBM8X_iEAATu0G@mail.gmail.com> (raw)
In-Reply-To: <B3BEB66D-49FF-48B7-B40A-77A9B05F2B54@gmail.com>

Btrfs has its own wiki page at https://btrfs.wiki.kernel.org which you
may find more helpful than what is on wikipedia.

2011/1/20 Beno=EEt Thi=E9bault <benoit.thiebault@gmail.com>:
> Thanks for your answer
>
> Le 20 janv. 2011 =E0 22:20, Chris Mason a =E9crit :
>
>> 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.
>
> Maybe the wikipedia article should be modified then, because it is no=
t very reinsuring :-)
>
>> A final release? =A0We'll keep improving things for a long time. =A0=
The
>> biggest missing feature today is btrfsck, which I'm working on full =
time
>> right now.
>>
>> -chris
>
> Still on the wikipedia page, it's written "Btrfs 1.0 (with finalized =
on-disk format) was originally slated for a late 2008 release,[5] but a=
 stable release has not been made as of January 2011.", which is also v=
ery confusing.
>
> According to you, is the version of btrfs in 2.6.37 ready for product=
ion? I mean, are there still chances that I may loose all my data if I =
use btrfs?
>
> Last question, do you know when the RAID-5 like capabilities will be =
available?
>
> Sorry to ask so many questions, I fully understand you and your team =
are working very hard on the project, but I was very confused by the Wi=
kipedia article.
>
> Kind regards,
>
> Ben--
> 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 =A0http://vger.kernel.org/majordomo-info.html
>
--
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

  reply	other threads:[~2011-01-21  6:46 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
2011-01-21  5:25   ` Benoît Thiébault
2011-01-21  6:46     ` Chester [this message]
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=AANLkTikGPRrdaj2SO5ZwjD8pZEVNj4pBM8X_iEAATu0G@mail.gmail.com \
    --to=somethingsome2000@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).