From: Chris Mason <chris.mason@oracle.com>
To: Ameya Palande <ameya.palande@nokia.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 2.6.36-rc1 btrfs still unstable
Date: Mon, 16 Aug 2010 08:16:58 -0400 [thread overview]
Message-ID: <20100816121658.GT3315@think> (raw)
In-Reply-To: <1281948382.1888.7.camel@chotu>
On Mon, Aug 16, 2010 at 11:46:22AM +0300, Ameya Palande wrote:
> Hi Chris,
>
> Today I was checking the Kconfig option for btrfs and it still says,
> "Btrfs filesystem (EXPERIMENTAL) Unstable disk format"
>
> I remember that some time back we had discussion about this on meego-dev
> mailing list:
> http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg04881.html
>
> In case if you have forgotten about this, then can we still change this
> for 36-rc2?
Yes, I'll go ahead and send this one in.
I've spent a great deal of time trying to nail down the interaction
between raid56 stripe size and adding/removing volumes from the FS
(basically restriping the raid).
The end result just isn't as user friendly as I wanted yet, but the raid
code is holding up very well.
-chris
next prev parent reply other threads:[~2010-08-16 12:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 8:46 2.6.36-rc1 btrfs still unstable Ameya Palande
2010-08-16 12:16 ` Chris Mason [this message]
2010-08-16 14:17 ` Morten P.D. Stevens
2010-08-16 15:45 ` Chris Ball
[not found] ` <AANLkTin-q4N9g3=ymsiJy051xts3b2vioNdqku6DMEzQ@mail.gmail.com>
2010-08-16 16:11 ` Fwd: " Evert Vorster
2010-08-16 16:32 ` Chris Ball
2010-08-16 22:25 ` Diego Calleja
2010-08-26 22:45 ` Roy Sigurd Karlsbakk
2010-08-26 23:17 ` Diego Calleja
2010-08-17 11:57 ` Carlos R. Mafra
2010-08-17 16:25 ` Rodrigo E. De León Plicet
2010-08-25 16:57 ` Johannes Hirte
2010-08-26 8:58 ` Xavier Nicollet
2010-08-26 22:48 ` Roy Sigurd Karlsbakk
2010-08-17 0:14 ` Chris Samuel
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=20100816121658.GT3315@think \
--to=chris.mason@oracle.com \
--cc=ameya.palande@nokia.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).