[systemd-devel] name=systemd cgroup mounts/hierarchy

Andrei Enshin b1os at bk.ru
Thu Nov 12 17:05:34 UTC 2020


Hello systemd folks,

I have a k8s cluster on CoreOS which uses systemd.
There are few nodes after k8s update started to have (maybe it was before) a problem with the following mount:

mount ID           2826
parent ID           26
major:minor       0:23
root                    /kubepods/burstable/pod7ffde41a-fa85-4b01-8023-69a4e4b50c55/8842def241fac72cb34fdce90297b632f098289270fa92ec04643837f5748c15
mount point       /sys/fs/cgroup/systemd/kubepods/burstable/pod7ffde41a-fa85-4b01-8023-69a4e4b50c55/8842def241fac72cb34fdce90297b632f098289270fa92ec04643837f5748c15
mount options   rw,nosuid,nodev,noexec,relatime
optional fields    shared:6
separator           -
filesystem type  cgroup
mount source    cgroup
super options    rw,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd


It was taken from /proc/self/mountinfo


Here is also expected mount:
mount ID           26
parent ID           25
major:minor       0:23
root                    /
mount point       /sys/fs/cgroup/systemd
mount options   rw,nosuid,nodev,noexec,relatime
optional fields    shared:6
separator           -
filesystem type  cgroup
mount source    cgroup
super options    rw,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd


May I ask, does systemd mount on a fly some hierarchies like this and if yes what logic behind it?
 
---
Best Regards,
Andrei Enshin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20201112/9ce931ac/attachment.htm>


More information about the systemd-devel mailing list