From: NeilBrown <neilb@suse.de>
To: Prakash Punnoor <prakash@punnoor.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: udiskd high CPU usage with 4.0 git
Date: Mon, 16 Mar 2015 10:43:31 +1100 [thread overview]
Message-ID: <20150316104331.5a2c67d8@notabene.brown> (raw)
In-Reply-To: <54FDC061.2030006@punnoor.de>
[-- Attachment #1: Type: text/plain, Size: 2125 bytes --]
On Mon, 09 Mar 2015 16:46:41 +0100 Prakash Punnoor <prakash@punnoor.de> wrote:
> On 09.03.2015 00:30, NeilBrown wrote:
> > On Sun, 08 Mar 2015 18:14:39 +0100 Prakash Punnoor <prakash@punnoor.de> wrote:
> >
> >> Hi,
> >>
> >> I noticed the udisks daemon (version 2.1.4) suddenly started using high
> >> cpu (one core at 100%) with linux 4.0 git kernel. I bisected it to:
> >>
> >> 750f199ee8b578062341e6ddfe36c59ac8ff2dcb
> >>
> >> And reverting it from current master (at
> >> 2cf3afcd4cbe0e32b8722fc291e9255de1b4d6c6) fixes my problem indeed.
> >>
> >> I attached dmesg and config from
> >> 2cf3afcd4cbe0e32b8722fc291e9255de1b4d6c6 with
> >> 750f199ee8b578062341e6ddfe36c59ac8ff2dcb reverted. Any more infos
> >> needed? I am actually using a raid5 array, if that matters:
> >>
> >> Personalities : [raid6] [raid5] [raid4]
> >> md127 : active raid5 sdd1[1] sdb1[3] sdc1[0]
> >> 3907023872 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3]
> >> [UUU]
> >>
> >> unused devices: <none>
> >>
> >>
> >> The array uses systemd automount feature (x-systemd.automount).
> >>
> >> Please CC me, as I am not subscribed.
> >>
> >>
> >> Regards,
> >>
> >> Prakash
> >
> > Thanks for the report.
> > I can't reproduce this, or see what would cause it.
> >
> > Can you please reproduce the problem and then run
> >
> > strace -o /tmp/udisks.trace -f -p `pidof udisksd`
> >
> > for a few seconds, then interrupt and post the resulting '/tmp/udisks.trace'.
>
> Hi, attached the trace.
>
>
Thanks.
The significant part is:
329 poll([{fd=4, events=POLLIN}, {fd=8, events=0}, {fd=9, events=0}, {fd=11, events=POLLIN}, {fd=13, events=0}, {fd=12, events=0}], 6, 513377) = 2 ([{fd=4, revents=POLLIN}, {fd=12, revents=POLLERR}])
repeating frequently, so fd4 and fd12 are always ready.
I don't know about fd4, but fd12 is:
329 read(12, "idle\n", 1024) = 5
so that is .../md/sync_action
It is simply always readable. I thought I had checked that, but it seems not.
Anyway I have a fix which I will post shortly.
thanks again,
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-03-15 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 17:14 udiskd high CPU usage with 4.0 git Prakash Punnoor
2015-03-08 23:30 ` NeilBrown
2015-03-09 15:46 ` Prakash Punnoor
2015-03-15 23:43 ` NeilBrown [this message]
2015-03-14 20:16 ` Torsten Kaiser
2015-03-15 23:44 ` NeilBrown
2015-03-16 7:16 ` Torsten Kaiser
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=20150316104331.5a2c67d8@notabene.brown \
--to=neilb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=prakash@punnoor.de \
/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