All of lore.kernel.org
 help / color / mirror / Atom feed
From: "João Eduardo Luís" <jecluis@gmail.com>
To: Martin Mailand <martin@tuxadero.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Strange write behavior on an osd
Date: Tue, 24 Apr 2012 17:31:42 +0100	[thread overview]
Message-ID: <4F96D56E.1080205@gmail.com> (raw)
In-Reply-To: <4F96CF81.4030707@tuxadero.com>

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]

On 04/24/2012 05:06 PM, Martin Mailand wrote:
> Hi,
> 
> Am 24.04.2012 17:23, schrieb João Eduardo Luís:
>> Any chance you could run iotop during the busy periods and tell us which
>> processes are issuing the io?
> 
> sure,
> http://85.214.49.87/ceph/iotop.txt
> 
> -martin
> 

I don't want to rush into a definite answer, but it looks like the IO
bursts are caused by btrfs. The periods on which they happen are
consistent with btrfs' internal thread scheduling (which are fired every
30 seconds), and from iotop it would seem as if they're the ones
responsible for all the IO when it jumps from the "couple of MB/s" mark
to "several hundreds of MB/s".

I've seen it happen before, although on synthetic and very specific
workloads. Not sure on what may be the cause in your case though.

What kernel and btrfs versions are you using?

-- 
João Eduardo Luís
gpg key: 477C26E5 from pool.keyserver.eu


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]

  reply	other threads:[~2012-04-24 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 14:32 Strange write behavior on an osd Martin Mailand
2012-04-24 15:23 ` João Eduardo Luís
2012-04-24 16:06   ` Martin Mailand
2012-04-24 16:31     ` João Eduardo Luís [this message]
2012-04-24 17:39       ` 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=4F96D56E.1080205@gmail.com \
    --to=jecluis@gmail.com \
    --cc=ceph-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.