All of lore.kernel.org
 help / color / mirror / Atom feed
From: "K. Richard Pixley" <rich@noir.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: server goes pathological
Date: Sat, 14 Aug 2010 09:55:46 -0700	[thread overview]
Message-ID: <4C66CA92.6030808@noir.com> (raw)

  Ubuntu-10.04, x86, stock.

I'm running into a situation where a server goes pathological.  
Basically, it becomes excruciatingly slow.  I can get things through the 
file system, but a simple file touch can take 6 - 12 hours.

Top shows various btrfs processes hard at work - typically 100% of a 
cpu, (four cpu server), and the machine shows a load of just over 4.  
Some flush-btrfs, some btrfs-transacti, occasional others.

File system is was created with "mkfs.btrfs -m single -d single".

The same, (or a substantially similar), problem has arisen once so far 
on each of three different servers, so I have a good  indication that 
it's not a hardware error.

Aside from rebooting, and rebuilding the file system, is there anything 
I can do to clear this state?

Is there any other information I can provide to help debug either what's 
going on with my server and/or btrfs?

--rich

                 reply	other threads:[~2010-08-14 16:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4C66CA92.6030808@noir.com \
    --to=rich@noir.com \
    --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 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.