From: Jeremy Sanders <jeremy@jeremysanders.net>
To: linux-btrfs@vger.kernel.org
Cc: ceph-devel@vger.kernel.org
Subject: Re: Btrfs slowdown
Date: Mon, 25 Jul 2011 15:37:51 +0100 [thread overview]
Message-ID: <j0jv3v$fa6$1@dough.gmane.org> (raw)
In-Reply-To: CAO47_-9BLKWUGDEuzaLqHSq9tZkAUaO8FMQEy1pPk9A2Hb+5AQ@mail.gmail.com
Christian Brunner wrote:
> we are running a ceph cluster with btrfs as it's base filesystem
> (kernel 3.0). At the beginning everything worked very well, but after
> a few days (2-3) things are getting very slow.
We get quite a slowdown over time, doing rsyncs to different snapshots.
Btrfs seems to go from using several threads in parallel btrfs-endio-0,1,2,
shown in top, to just using a single thread btrfs-delalloc.
Jeremy
next prev parent reply other threads:[~2011-07-25 14:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 7:54 Btrfs slowdown Christian Brunner
2011-07-25 8:51 ` Andrej Podzimek
2011-07-25 9:45 ` Andrej Podzimek
2011-08-03 15:56 ` mck
2011-07-25 14:37 ` Jeremy Sanders [this message]
2011-07-25 19:52 ` Chris Mason
2011-07-27 8:41 ` Christian Brunner
2011-07-28 4:05 ` Marcus Sorensen
2011-07-28 15:10 ` Christian Brunner
2011-07-28 16:01 ` Sage Weil
2011-08-08 21:58 ` Sage Weil
2011-08-09 13:33 ` Christian Brunner
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='j0jv3v$fa6$1@dough.gmane.org' \
--to=jeremy@jeremysanders.net \
--cc=ceph-devel@vger.kernel.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).