All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hubert Kario <hka@qbs.com.pl>
To: "Benoît Thiébault" <benoit.thiebault@gmail.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs, broken design?
Date: Fri, 21 Jan 2011 09:21:30 +0100	[thread overview]
Message-ID: <201101210921.30427.hka@qbs.com.pl> (raw)
In-Reply-To: <06598C10-801F-4969-83F9-9BB3B9149488@gmail.com>

On Friday 21 of January 2011 09:11:57 Beno=EEt Thi=E9bault wrote:
> Ok, thanks, I will read the project wiki more carefully then :-)
> Beware however that Wikipedia is the first place to look for informat=
ion
> for a lot of people (whether this is a good practice or not) and it
> currently does not provide a very good advertisement to btrfs.

It's still aimed more at experts than even to advanced users, though th=
is will=20
change when btrfsck will become avaiable.
=20
> Le 21 janv. 2011 =E0 07:46, Chester a =E9crit :
> > Btrfs has its own wiki page at https://btrfs.wiki.kernel.org which =
you
> > may find more helpful than what is on wikipedia.
> >=20
> > 2011/1/20 Beno=EEt Thi=E9bault <benoit.thiebault@gmail.com>:
> >> Thanks for your answer
> >>=20
> >> 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 a=
lso
> >>> better described the way the tree balancing works to Edward.
> >>=20
> >> Maybe the wikipedia article should be modified then, because it is=
 not
> >> very reinsuring :-)
> >>=20
> >>> A final release?  We'll keep improving things for a long time.  T=
he
> >>> biggest missing feature today is btrfsck, which I'm working on fu=
ll
> >>> time right now.
> >>>=20
> >>> -chris
> >>=20
> >> Still on the wikipedia page, it's written "Btrfs 1.0 (with finaliz=
ed
> >> 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 al=
so
> >> very confusing.
> >>=20
> >> According to you, is the version of btrfs in 2.6.37 ready for
> >> production? I mean, are there still chances that I may loose all m=
y
> >> data if I use btrfs?
> >>=20
> >> Last question, do you know when the RAID-5 like capabilities will =
be
> >> available?
> >>=20
> >> Sorry to ask so many questions, I fully understand you and your te=
am are
> >> working very hard on the project, but I was very confused by the
> >> Wikipedia article.
> >>=20
> >> Kind regards,
> >>=20
> >> Ben--
> >> To unsubscribe from this list: send the line "unsubscribe linux-bt=
rfs"
> >> in the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >=20
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btr=
fs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>=20
> --
> 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

--=20
Hubert Kario
QBS - Quality Business Software
02-656 Warszawa, ul. Ksawer=F3w 30/85
tel. +48 (22) 646-61-51, 646-74-24
www.qbs.com.pl
--
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  8:21 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
2011-01-21  8:11       ` Benoît Thiébault
2011-01-21  8:21         ` Hubert Kario [this message]
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=201101210921.30427.hka@qbs.com.pl \
    --to=hka@qbs.com.pl \
    --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 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.