From: Adrian Ulrich <adrian@blinkenlights.ch>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-cache processes
Date: Sun, 9 Aug 2009 00:17:23 +0200 [thread overview]
Message-ID: <20090809001723.223a0962.adrian@blinkenlights.ch> (raw)
Hi,
I've upgraded my system to 2.6.31-rc5 some days ago. Yesterday i've discovered that
this kernel produces some berserk btrfs-cache processes:
There are about 4 of them and they use ~95% sys-cputime.
About 20 seconds after they started 'freaking out' all writes to BTRFS will
block and umounting also doesn't work anymore. Reading the volume
still works (mostly) and there appers to be no disk activity (iostat/top
reports nothing unusual).
This isn't normal, isn't it? ;-)
Everything appears to work fine on Linux 2.6.31-rc3
Regards,
Adrian
next reply other threads:[~2009-08-08 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 22:17 Adrian Ulrich [this message]
2009-08-09 4:00 ` btrfs-cache processes Yan Zheng
2009-08-09 12:51 ` Adrian Ulrich
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=20090809001723.223a0962.adrian@blinkenlights.ch \
--to=adrian@blinkenlights.ch \
--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