High CPU usage by gvfs-udisks2-vo which is caused by microk8s
See original GitHub issuePlease run microk8s.inspect
and attach the generated tarball to this issue.
inspection-report-20190610_165704.tar.gz
We appreciate your feedback. Thank you for using microk8s.
top
shows:
2293 khteh 20 0 270176 26568 7776 R 56.7 0.1 198:27.51 gvfs-udisks2-vo
udisksctl monitor
shows it is mainly by microk8s. What happen?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:13
- Comments:24 (11 by maintainers)
Top Results From Across the Web
High CPU usage by gvfs-udisks2-vo which is caused ... - GitHub
udisksctl monitor shows it is mainly by microk8s. What happen?
Read more >High CPU usage by gvfs-udisks2-vo caused by microk8s
Hi, We get reports from users seeing high cpu usage. This does not seem to be related to snapcraft, but one of the...
Read more >Troubleshooting - MicroK8s
Full high availability Kubernetes with autonomous clusters. ... You can then use kubectl to view the log. ... My pods are not starting...
Read more >Microk8s CPU spike - Discuss Kubernetes
large vm to host my microk8s cluster to run my applications. I am using microk8s 1.21/stable. Recently, around Dec 5, I saw the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI I have this on a ubuntu 20.04 system with kubernetes installed using kubespray.
I did use microk8s at one point, but had already stopped it.
Interestingly if I run nautilus on this machine, it freezes. Same with all browser file save dialogs.
Running
Fixes both the 100% CPU issue, and makes nautilus stop from freezing
I’m getting this issue when deploying Kubeflow, which has lots of pods that require storage. Since I’m not running the cluster full-time, I was able to work around this by running
systemctl stop --user gvfs-udisks2-volume-monitor
to disable thegvfs-udisks2-volume-monitor
process.Also, I tried adding the
x-gvfs-hide
option to all of the mounts, which didn’t seem to help.udisksctl monitor
showed very few events (unlike before adding the option), butgvfs-udisks2-volume-monitor
still ate up CPU. It’s possible that’s due to me remounting with the flag instead of mounting with the flag. Here’s what I ran to add the flag: