various /run/credentials/... tmpfs mounts lingering
Dear tumbleweeders, I just noticed that with recent tw updates, probably starting with systemd 256, quite a number of tmpfs instances remain mounted after booting, with names corresponding to systemd services. Some of these services are one-shot and long gone. Shouldn't at least these, then vanish again? See below for what I mean. I haven't checked whether that would be upstream behaviour but thought I mention it regardless, here, as it's bound to be seen by others. best regards Patrick tmpfs 1024 0 1024 0% /run/credentials/systemd-tmpfiles-setup-dev-early.service tmpfs 1024 0 1024 0% /run/credentials/systemd-journald.service tmpfs 1024 0 1024 0% /run/credentials/systemd-udev-load-credentials.service tmpfs 1024 0 1024 0% /run/credentials/systemd-tmpfiles-setup-dev.service tmpfs 1024 0 1024 0% /run/credentials/systemd-vconsole-setup.service tmpfs 1024 0 1024 0% /run/credentials/systemd-sysctl.service tmpfs 1024 0 1024 0% /run/credentials/systemd-tmpfiles-setup.service tmpfs 1024 0 1024 0% /run/credentials/getty@tty1.service
On Friday 2024-08-09 17:37, Patrick Schaaf via openSUSE Factory wrote:
I just noticed that with recent tw updates, probably starting with systemd 256, quite a number of tmpfs instances remain mounted after booting, with names corresponding to systemd services. Some of these services are one-shot and long gone. Shouldn't at least these, then vanish again?
systemctl status systemd-tmpfiles-setup-dev.service: Active: active (exited) since Fri 2024-08-09 06:11:07 CEST; 11h ago What matters is the status of the unit, not the status of the process.
Am 09.08.24 um 18:10 schrieb Jan Engelhardt:
On Friday 2024-08-09 17:37, Patrick Schaaf via openSUSE Factory wrote:
I just noticed that with recent tw updates, probably starting with systemd 256, quite a number of tmpfs instances remain mounted after booting, with names corresponding to systemd services. Some of these services are one-shot and long gone. Shouldn't at least these, then vanish again?
systemctl status systemd-tmpfiles-setup-dev.service:
Active: active (exited) since Fri 2024-08-09 06:11:07 CEST; 11h ago
What matters is the status of the unit, not the status of the process.
But these mounts are presumably only usable by active processes, right? Not sure if the data is intentionally kept around for another run of the one-shot service though. Aaron
I still see this behavior on 20240903. Is this expected or a bug ? On 8/9/24 11:37 AM, Patrick Schaaf via openSUSE Factory wrote:
Dear tumbleweeders,
I just noticed that with recent tw updates, probably starting with systemd 256, quite a number of tmpfs instances remain mounted after booting, with names corresponding to systemd services. Some of these services are one-shot and long gone. Shouldn't at least these, then vanish again? See below for what I mean.
I haven't checked whether that would be upstream behaviour but thought I mention it regardless, here, as it's bound to be seen by others.
best regards Patrick
tmpfs 1024 0 1024 0% /run/credentials/systemd-tmpfiles-setup-dev-early.service tmpfs 1024 0 1024 0% /run/credentials/systemd-journald.service tmpfs 1024 0 1024 0% /run/credentials/systemd-udev-load-credentials.service tmpfs 1024 0 1024 0% /run/credentials/systemd-tmpfiles-setup-dev.service tmpfs 1024 0 1024 0% /run/credentials/systemd-vconsole-setup.service tmpfs 1024 0 1024 0% /run/credentials/systemd-sysctl.service tmpfs 1024 0 1024 0% /run/credentials/systemd-tmpfiles-setup.service tmpfs 1024 0 1024 0% /run/credentials/getty@tty1.service
-- Regards, Joe
participants (4)
-
Aaron Puchert -
Jan Engelhardt -
Joe Salmeri -
Patrick Schaaf