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 16:23:03 +0100 [thread overview]
Message-ID: <4F96C557.4090603@gmail.com> (raw)
In-Reply-To: <4F96B971.5050806@tuxadero.com>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
On 04/24/2012 03:32 PM, Martin Mailand wrote:
> Hi,
> I have a strange behavior on the osd, the cluster is a two node system,
> on one machine 50 qemu/rbd vm's are running (idling) the other machine
> is a osd with four osd processes and one mon processes.
>
> The osd disk are as follow
>
> sda is root
> sdb is journal four partitions
> sd{c,d,e,f) each three disk via a raid controler.
>
> /dev/sdc on /data/osd.0 type btrfs
> (rw,noatime,nodiratime,nodatacow,autodefrag)
> /dev/sdd on /data/osd.1 type btrfs
> (rw,noatime,nodiratime,nodatacow,autodefrag)
> /dev/sde on /data/osd.2 type btrfs
> (rw,noatime,nodiratime,nodatacow,autodefrag)
> /dev/sdf on /data/osd.3 type btrfs
> (rw,noatime,nodiratime,nodatacow,autodefrag)
>
>
> There is almost no network traffic, but the osd writes huge amount to
> the disk for around 90 sec and then its almost idle for 30 sec, the
> writes always goes to sde.
>
> Why is it so bursty?
>
> [snip]
Any chance you could run iotop during the busy periods and tell us which
processes are issuing the io?
--
João Eduardo Luís
gpg key: 477C26E5 from pool.keyserver.eu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]
next prev parent reply other threads:[~2012-04-24 15:23 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 [this message]
2012-04-24 16:06 ` Martin Mailand
2012-04-24 16:31 ` João Eduardo Luís
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=4F96C557.4090603@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox