From: "Jérôme Carretero" <cJ-ko@zougloub.eu>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [weird] High CPU usage caused by btrfs-transaction thread busy doing find_next_zero_bit()
Date: Wed, 14 Mar 2012 23:16:16 -0400 [thread overview]
Message-ID: <20120314231616.601de469@Bidule> (raw)
In-Reply-To: <20120222112021.2c8c4d4b@Malcolm>
On Wed, 22 Feb 2012 11:20:21 -0500
J=C3=A9r=C3=B4me Carretero <cJ-ko@zougloub.eu> wrote:
> My filesystem is super-sluggish since about a week, and perf top tell=
s me
> that find_next_bit(), find_next_zero_bit() is eating my netbook's CPU=
=2E
>=20
> The kernel is 3.3-rc3+188 (g3ec1e88) and I don't use this laptop a lo=
t,
> so I'm ready to cooperate.
This machine was updated to today's kernel, and behaves same as before.
scrub says nothing, but btrfsck doesn't like to be run.
Does this interest someone (metadump image) or I can reformat the drive=
?
Regards,
--=20
cJ
--
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
prev parent reply other threads:[~2012-03-15 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 16:20 [weird] High CPU usage caused by btrfs-transaction thread busy doing find_next_zero_bit() Jérôme Carretero
2012-03-15 3:16 ` Jérôme Carretero [this message]
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=20120314231616.601de469@Bidule \
--to=cj-ko@zougloub.eu \
--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).