Package: systemd
Version: 257.13-1~deb13u1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I have a /mnt/boot/ filesystem specified in /etc/fstab that is moutned on
each boot:
/dev/disk/by-id/scsi-20010b9fd080ccf7e-part2 /mnt/boot spadfs defaults 0 2
* What exactly did you do (or not do) that was effective (or
ineffective)?
I tried to unmount the filesystem with this command:
umount /mnt/boot
and spin down the disk with this command:
sdparm -r -C stop /dev/disk/by-id/scsi-20010b9fd080ccf7e
* What was the outcome of this action?
The filesystem disappeared from /mnt/boot, but it was not unmounted; it
was reporting I/O errors because the disk was spun down.
* What outcome did you expect instead?
The umount command should unmount a filesystem.
I was analyzing this problem and it turned out that the /mnt/boot
filesystem was not unmounted because it was still kept mounted in
namespaces of two daemons - rsyslog and virtlogd.
grep boot /proc/*/mountinfo showed:
/proc/1686/mountinfo:508 402 8:50 / /mnt/boot rw,relatime shared:156 - spadfs
/dev/sdd2
rw,umask=022,prealloc_part=8,prealloc_min=4096,prealloc_max=1048576,xfer_size=524288,buffer_size=4096,prefetch=524288,sync_time=120,no_checksums,ino64=no
/proc/1686/mountinfo:405 508 8:50 /boot /mnt/boot/boot ro,nosuid,relatime
shared:157 - spadfs /dev/sdd2
rw,umask=022,prealloc_part=8,prealloc_min=4096,prealloc_max=1048576,xfer_size=524288,buffer_size=4096,prefetch=524288,sync_time=120,no_checksums,ino64=no
/proc/1694/mountinfo:396 245 8:50 / /mnt/boot rw,relatime shared:195 - spadfs
/dev/sdd2
rw,umask=022,prealloc_part=8,prealloc_min=4096,prealloc_max=1048576,xfer_size=524288,buffer_size=4096,prefetch=524288,sync_time=120,no_checksums,ino64=no
/proc/1694/mountinfo:249 396 8:50 /boot /mnt/boot/boot ro,relatime shared:196 -
spadfs /dev/sdd2
rw,umask=022,prealloc_part=8,prealloc_min=4096,prealloc_max=1048576,xfer_size=524288,buffer_size=4096,prefetch=524288,sync_time=120,no_checksums,ino64=no
When I restarted the daemons with:
systemctl restart rsyslog
systemctl restart virtlogd
the filesystem was truly unmounted.
I think that systemd shouldn't clone the mount namespace to various
daemons and make filesystems non-unmountable.
This problem started to happen after upgrade to Debian 13. I didn't
observe it with previous releases.
Mikulas
-- Package-specific info:
-- System Information:
Debian Release: 13.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64, armel, armhf, ppc64el, s390x
Kernel: Linux 7.1.5 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii libacl1 2.3.2-2+b1
ii libapparmor1 4.1.0-1
ii libc6 2.41-12+deb13u4
ii libmount1 2.41.5-0+deb13u1
ii libpam0g 1.7.0-5
ii libseccomp2 2.6.0-2
ii libselinux1 3.8.1-1
ii libssl3t64 3.5.7-1~deb13u2
ii libsystemd-shared 257.13-1~deb13u1
ii libsystemd0 257.13-1~deb13u1
ii mount 2.41.5-0+deb13u1
Versions of packages systemd recommends:
ii dbus [default-dbus-system-bus] 1.16.2-2
ii linux-sysctl-defaults 4.12.1
ii ntpsec [time-daemon] 1.2.3+dfsg1-8
pn systemd-cryptsetup <none>
Versions of packages systemd suggests:
pn libtss2-tcti-device0 <none>
ii polkitd 126-2
pn systemd-boot <none>
ii systemd-container 257.13-1~deb13u1
pn systemd-homed <none>
pn systemd-repart <none>
pn systemd-resolved <none>
pn systemd-userdbd <none>
Versions of packages systemd is related to:
ii dbus-user-session 1.16.2-2
pn dracut <none>
ii initramfs-tools 0.148.4
pn libnss-systemd <none>
ii libpam-systemd 257.13-1~deb13u1
ii udev 257.13-1~deb13u1
-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
NAutoVTs=12
-- no debconf information
