-
Notifications
You must be signed in to change notification settings - Fork 65
Open
Description
Problem: diod 1.1.0 appears to leak memory during multi-user operation.
I have home directories mounted via 9P on some test nodes. When hitting it with a compilation workload on one node/one user, the diod memory usage as reported by `systemctl status diod`` shot up to 338M.
Early, before a recent restart, I had noticed it was up to nearly a gig.
Shutting down all the clients did not reduce the footprint (much)
● diod.service - 9P File Server
Loaded: loaded (/lib/systemd/system/diod.service; enabled; preset: enabled)
Active: active (running) since Tue 2025-11-25 07:13:00 PST; 2h 0min ago
Main PID: 780 (diod)
Tasks: 20 (limit: 9575)
Memory: 335.7M
CPU: 4min 10.358s
CGroup: /system.slice/diod.service
└─780 /usr/sbin/diod
Nov 25 07:13:00 picl0 systemd[1]: Starting diod.service - 9P File Server...
Nov 25 07:13:00 picl0 systemd[1]: Started diod.service - 9P File Server.
Nov 25 07:13:00 picl0 diod[780]: Listening on 0.0.0.0:564
Nov 25 07:13:00 picl0 diod[780]: Anyone can attach and access files as themselves
Nov 25 07:13:00 picl0 diod[780]: MUNGE authentication is required
Nov 25 07:31:04 picl0 diod[780]: checkauth(root@picl4:/nfshome): munge cred decode: Expired credential
Nov 25 07:31:04 picl0 diod[780]: attach(0@picl4:/nfshome): checkauth: Operationnot permitted
Metadata
Metadata
Assignees
Labels
No labels