I was looking into htop and the only process having > 0.0% CPU (apart from htop itself) was /usr/lib/udisks/udisks-daemon.

So the questions are: What is this service? Do I need it? (Or when do I need it?) Why is it accessing the drives?


Official package description for udisks:

The udisks daemon serves as an interface to system block devices, implemented via D-Bus. It handles operations such as querying, mounting, unmounting, formatting, or detaching storage devices such as hard disks or USB thumb drives.

This package also provides the udisks utility, which can be used to trigger these operations from the command line (if permitted by PolicyKit). External tools such as hdparm are used if available to implement extra operations, such as configuring disk spindown times.

Creating or modifying file systems such as XFS, RAID, or LUKS encryption requires that the corresponding mkfs.* and admin tools are installed, such as dosfstools and mtools for VFAT, xfsprogs for XFS, or cryptsetup for LUKS.

Do I need it?

This should be considered an essential package by almost everyone. The only time I would consider removing it is if I had a simple /dev/sdX CLI install on a machine where there was no need for udev -- i.e., the hardware never changes (which in practice almost always means a virtual machine, a VPS or a very very old machine).


Here is another take on your second question about whether you need it: It depends on what your objectives are. If you want to learn about how your system works under the hood, you definitely do not need any udisks daemon. Not even on Ubuntu.

I am speaking out of my own experience here. The world needs more people who are curious about what is going on under the hood. See my code on GitHub for reference.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.