From: Josef Bacik <josef@redhat.com>
To: Jim Hughes <jhughes@ctio.noao.edu>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Wretched Excess - a 62T btrfs filesystem
Date: Thu, 4 Mar 2010 15:37:47 -0500 [thread overview]
Message-ID: <20100304203744.GA8678@localhost.localdomain> (raw)
In-Reply-To: <4B8E787C.4080001@ctio.noao.edu>
On Wed, Mar 03, 2010 at 11:55:56AM -0300, Jim Hughes wrote:
> Folks:
>
> Thought you all might be interested to know we've just built a
> "Backblaze Pod" (see
> http://blog.backblaze.com/2009/09/01/petabytes-on-a-budget-how-to-build-cheap-cloud-storage/)
> running Fedora 12 and your latest (as of yesterday) GIT kernel snapshot.
>
> We mounted *all 45 disks* into one huge 62Tb btrfs RAID10 filesystem,
> and so far it works just great!
>
> I'd be interested in your comments as to pitfall, problems you all see
> in creating such a huge btrfs file system...
>
Well thats cool. The only thing that may start to cause problems is as you fill
it up, the time it takes to cache block groups is going to take _forever_.
Thankfully we only cache block groups on demand, and we try to do it in a way
that we save the crappiest ones for last, so even that probably won't be
terrible. As of right now balance's will _suck_, since they try to move all
block groups, but IIRC Yan is working on making balances take less time. Other
than that everything should work just as well as if it were a 10gb volume.
Thanks,
Josef
prev parent reply other threads:[~2010-03-04 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 14:55 Wretched Excess - a 62T btrfs filesystem Jim Hughes
2010-03-04 20:37 ` Josef Bacik [this message]
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=20100304203744.GA8678@localhost.localdomain \
--to=josef@redhat.com \
--cc=jhughes@ctio.noao.edu \
--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