gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
On Ubuntu 22.04.3 desktop, when running a k3s workload that uses volumes (using default local-path storageClass), process gvfs-disks2-
Even if the actual k3s workload is idle.
Steps To Reproduce:
- Use or install a desktop Ubuntu 22.04.3 (with default settings)
- Install K3s on it (current version is "v1.28.4+k3s2"), with default settings: "curl -sfL https:/
- Deploy k8s manifests with many volumes, like https:/
- Check CPU consumption on the host, with top, gnome-system-
Expected behavior:
Gnome desktop tools should not interfere with k3s.
Actual behavior:
Processes gvfs-disks2-
Same CPU consumption if you then remove the workload ("sudo k3s kubectl delete -f deployment-
I have other workloads (with data in PVs) where this CPU consumption is always there, when the workload is running (even if idle)
Additional context:
The symptoms are very similar to https:/
Executing "systemctl stop --user gvfs-udisks2-
Technical details:
k3s uses containerd to run containers. The local-path storageClass mounts local volumes (physically stored in /var/lib/
I suppose gnome applications try to scan these mount points. In this case, the solution might be to make them ignore them, a bit like https:/
NB: Was initially reported on https:/
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
I have the same behavior with Ubuntu 23.10.1 (with all current updates), using latest stable k3s (v1.28.5+k3s1)