From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Blog: "BTRFS is effectively stable"
Date: Sat, 30 Oct 2010 10:38:23 +1100 [thread overview]
Message-ID: <201010301038.28038.chris@csamuel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
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
# But it passed our stability test. 100 iterations (3.2TB
# written/read in all and compared to checksums) of the
# following fio test case.
[...]
# This is our baseline test. Failing RAIDs, failing drives,
# failing SSDs tend not to pass this test. Borked file systems
# tend not to pass this test. When something passes this test,
# again and again (3rd time we’ve run it), and does so without
# fail, we call it safe.
He has concerns about performance, but he's more interested
in reliability in these tests.
cheers!
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
next reply other threads:[~2010-10-29 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 23:38 Chris Samuel [this message]
2010-10-30 2:04 ` Blog: "BTRFS is effectively stable" Chris Ball
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=201010301038.28038.chris@csamuel.org \
--to=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).