From: Chris Ball <cjb@laptop.org>
To: Chris Samuel <chris@csamuel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Blog: "BTRFS is effectively stable"
Date: Fri, 29 Oct 2010 22:04:57 -0400 [thread overview]
Message-ID: <m3hbg48mgm.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <201010301038.28038.chris@csamuel.org> (Chris Samuel's message of "Sat, 30 Oct 2010 10:38:23 +1100")
Hi,
> A friend of mine who builds storage systems designed for HPC use
> has been keeping an eye on btrfs and has just done some testing
> of it with 2.6.36 and seems to like what he sees in terms of
> stability.
>
> http://scalability.org/?p=2711
This is nice to see, but we should be clearer about what stability
means. This was just fio testing; it doesn't say anything about
resilience to crashes, power offs, or the presence of corruption.
- Chris.
--
Chris Ball <cjb@laptop.org>
One Laptop Per Child
next prev parent reply other threads:[~2010-10-30 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 23:38 Blog: "BTRFS is effectively stable" Chris Samuel
2010-10-30 2:04 ` Chris Ball [this message]
2010-10-30 21:19 ` Freddie Cash
2010-10-30 22:02 ` Ahmed Kamal
2010-10-30 23:07 ` Joe Landman
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=m3hbg48mgm.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=chris@csamuel.org \
--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).