From: Chris Mason <chris.mason@oracle.com>
To: Martin Mailand <martin@tuxadero.com>
Cc: Josef Bacik <josef@redhat.com>, Christian Brunner <chb@muc.de>,
linux-btrfs@vger.kernel.org, ceph-devel@vger.kernel.org
Subject: Re: Btrfs slowdown with ceph (how to reproduce)
Date: Tue, 24 Jan 2012 14:40:44 -0500 [thread overview]
Message-ID: <20120124194044.GI4387@shiny> (raw)
In-Reply-To: <4F1F036E.9030801@tuxadero.com>
On Tue, Jan 24, 2012 at 08:15:58PM +0100, Martin Mailand wrote:
> Hi
> I tried the branch on one of my ceph osd, and there is a big
> difference in the performance.
> The average request size stayed high, but after around a hour the
> kernel crashed.
>
> IOstat
> http://pastebin.com/xjuriJ6J
>
> Kernel trace
> http://pastebin.com/SYE95GgH
Aha, this I know how to fix. Thanks for trying it out.
-chris
next prev parent reply other threads:[~2012-01-24 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 12:13 Btrfs slowdown with ceph (how to reproduce) Christian Brunner
2012-01-23 18:19 ` Josef Bacik
2012-01-23 18:50 ` Chris Mason
2012-01-23 20:53 ` Christian Brunner
2012-01-24 19:15 ` Martin Mailand
2012-01-24 19:40 ` Chris Mason [this message]
2012-01-24 20:55 ` Martin Mailand
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=20120124194044.GI4387@shiny \
--to=chris.mason@oracle.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chb@muc.de \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@tuxadero.com \
/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).