From: Chris Mason <chris.mason@oracle.com>
To: Christian Brunner <chb@muc.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Btrfs slowdown
Date: Mon, 25 Jul 2011 15:52:50 -0400 [thread overview]
Message-ID: <1311623446-sup-8105@shiny> (raw)
In-Reply-To: <CAO47_-9BLKWUGDEuzaLqHSq9tZkAUaO8FMQEy1pPk9A2Hb+5AQ@mail.gmail.com>
Excerpts from Christian Brunner's message of 2011-07-25 03:54:47 -0400:
> Hi,
>
> 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.
>
> When I look at the object store servers I see heavy disk-i/o on the
> btrfs filesystems (disk utilization is between 60% and 100%). I also
> did some tracing on the Cepp-Object-Store-Daemon, but I'm quite
> certain, that the majority of the disk I/O is not caused by ceph or
> any other userland process.
>
> When reboot the system(s) the problems go away for another 2-3 days,
> but after that, it starts again. I'm not sure if the problem is
> related to the kernel warning I've reported last week. At least there
> is no temporal relationship between the warning and the slowdown.
>
> Any hints on how to trace this would be welcome.
The easiest way to trace this is with latencytop.
Apply this patch:
http://oss.oracle.com/~mason/latencytop.patch
And then use latencytop -c for a few minutes while the system is slow.
Send the output here and hopefully we'll be able to figure it out.
-chris
next prev parent reply other threads:[~2011-07-25 19:52 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
2011-07-25 19:52 ` Chris Mason [this message]
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=1311623446-sup-8105@shiny \
--to=chris.mason@oracle.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chb@muc.de \
--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).