On 09.03.2015 00:30, NeilBrown wrote: > On Sun, 08 Mar 2015 18:14:39 +0100 Prakash Punnoor <prak...@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. Regards, Prakash
udisks.trace.xz
Description: application/xz
