linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrej Podzimek <andrej@podzimek.org>
To: chb@muc.de
Cc: linux-btrfs@vger.kernel.org, ceph-devel@vger.kernel.org
Subject: Re: Btrfs slowdown
Date: Mon, 25 Jul 2011 10:51:09 +0200	[thread overview]
Message-ID: <4E2D2E7D.3040303@podzimek.org> (raw)
In-Reply-To: <CAO47_-9BLKWUGDEuzaLqHSq9tZkAUaO8FMQEy1pPk9A2Hb+5AQ@mail.gmail.com>

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

Hello,

I can see something similar on the machines I maintain, mostly single-disk setups with a 2.6.39 kernel:

	1) Heavy and frequent disk thrashing, although less than 20% of RAM is used and no swap usage is reported.
	2) During the disk thrashing, some processors (usually 2 or 3) spend 100% of their time busy waiting, according to htop.
	3) Some userspace applications freeze for tens of seconds during the thrashing and busy waiting, sometimes even htop itself...

The problem has only been observed on 64-bit multiprocessors (Core i7 laptop and Nehalem class server Xeons). A 32-bit multiprocessor (Intel Core Duo) and a 64-bit uniprocessor (Intel Core 2 Duo class Celeron) do not seem to have any issues.

Furthermore, none of the machines had this problem with 2.6.38 and earlier kernels. Btrfs "just worked" before 2.6.39. I'll test 3.0 today to see whether some of these issues disappear.

Neither ceph nor any other remote/distributed filesystem (not even NFS) runs on the machines.

The second problem listed above looks like illegal blocking of a vital spinlock during a long disk operation, which freezes some kernel subsystems for an inordinate amount of time and causes a number of processors to wait actively for tens of seconds. (Needless to say that this is not acceptable on a laptop...)

Web browsers (Firefox and Chromium) seem to trigger this issue slightly more often than other applications, but I have no detailed statistics to prove this. ;-)

Two Core i7 class multiprocessors work 100% flawlessly with ext4, although their kernel configuration is otherwise identical to the machines that use Btrfs.

Andrej

> 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.
>
> Thanks,
> Christian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: Elektronický podpis S/MIME --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]

  reply	other threads:[~2011-07-25  8:51 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 [this message]
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
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=4E2D2E7D.3040303@podzimek.org \
    --to=andrej@podzimek.org \
    --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).