I've just hit a 100% udisks-daemon as well.. but it did stop by itself, after a LONG time (like 20-30'-ish, which surely isn't "normal" ?) - without me doing anything (I did NOT kill it; but maybe some... watcher process did?). It seems to have started about when I did a VirtualBox update - not sure if that could have anything to do with it?
> running an old unmaintained version of udisks. Please update to the udisks 2.x series.
I'm on what I think is a fairly standard out of the box Ubuntu 13.10, here is some info:
$ uname -a
Linux yoko 3.11.0-20-generic #35-Ubuntu SMP Fri May 2 21:32:49 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 13.10
Release: 13.10
Codename: saucy
$ dpkg -l | grep udisks
ii libudisks2-0:amd64 2.1.0-4ubuntu0.1 amd64 GObject based library to access udisks2
ii udisks 1.0.4-8ubuntu1.1 amd64 storage media interface
ii udisks2 2.1.0-4ubuntu0.1 amd64 D-BUS service to access and manipulate storage devices
I've tried to look into "Messages which appeared in journalctl" to help with this (when the problem was still going on), but I don't seem to have a command named 'journalctl' in Ubuntu 13.10 - what information would help you to understand the root cause of this better - should it happen again? (There was nothing in 'dmesg | grep udisks', which is probably normal; just say'n.) -- Attached vorburger_udisks_dump.txt is the result of having run 'udisks --dump' while it was spinning - though I doubt that there could be anything useful in that?
I don't know much science there is in the "not having quote mark at the first line of the locale" conspiracy theory, but just in case, here's mine (standard Ubuntu) :
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/381063 is an older (closed) but with something about "multiuser system with many desktop users, the system dbus-daemon process can easily exceed the 1024 open file..." - I thought it may be worthwhile to mention that in my case I did indeed have two completely separate desktop user sessions open and running.
I've just hit a 100% udisks-daemon as well.. but it did stop by itself, after a LONG time (like 20-30'-ish, which surely isn't "normal" ?) - without me doing anything (I did NOT kill it; but maybe some... watcher process did?). It seems to have started about when I did a VirtualBox update - not sure if that could have anything to do with it?
https:/ /bugs.launchpad .net/ubuntu/ +source/ udisks/ +bug/1282119 has others hitting this. Similar reports on https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1049928
> running an old unmaintained version of udisks. Please update to the udisks 2.x series.
I'm on what I think is a fairly standard out of the box Ubuntu 13.10, here is some info:
$ uname -a
Linux yoko 3.11.0-20-generic #35-Ubuntu SMP Fri May 2 21:32:49 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 13.10
Release: 13.10
Codename: saucy
$ dpkg -l | grep udisks
ii libudisks2-0:amd64 2.1.0-4ubuntu0.1 amd64 GObject based library to access udisks2
ii udisks 1.0.4-8ubuntu1.1 amd64 storage media interface
ii udisks2 2.1.0-4ubuntu0.1 amd64 D-BUS service to access and manipulate storage devices
I've tried to look into "Messages which appeared in journalctl" to help with this (when the problem was still going on), but I don't seem to have a command named 'journalctl' in Ubuntu 13.10 - what information would help you to understand the root cause of this better - should it happen again? (There was nothing in 'dmesg | grep udisks', which is probably normal; just say'n.) -- Attached vorburger_ udisks_ dump.txt is the result of having run 'udisks --dump' while it was spinning - though I doubt that there could be anything useful in that?
I don't know much science there is in the "not having quote mark at the first line of the locale" conspiracy theory, but just in case, here's mine (standard Ubuntu) :
$ locale "en_US. UTF-8" en_GB.UTF- 8 "en_US. UTF-8" en_GB.UTF- 8 "en_US. UTF-8" en_GB.UTF- 8 en_GB.UTF- 8 en_GB.UTF- 8 en_GB.UTF- 8 ON=en_GB. UTF-8
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE=
LC_NUMERIC=
LC_TIME=en_GB.UTF-8
LC_COLLATE=
LC_MONETARY=
LC_MESSAGES=
LC_PAPER=
LC_NAME=en_GB.UTF-8
LC_ADDRESS=
LC_TELEPHONE=
LC_MEASUREMENT=
LC_IDENTIFICATI
LC_ALL=
https:/ /bugs.launchpad .net/ubuntu/ +source/ dbus/+bug/ 381063 is an older (closed) but with something about "multiuser system with many desktop users, the system dbus-daemon process can easily exceed the 1024 open file..." - I thought it may be worthwhile to mention that in my case I did indeed have two completely separate desktop user sessions open and running.