Your message dated Wed, 08 Oct 2025 10:23:18 +0000
with message-id <[email protected]>
and subject line Bug#719249: fixed in sysvinit 3.15-3
has caused the Debian Bug report #719249,
regarding initscripts: mount-functions.sh creates .tmpfs files even when
mounting fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
719249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719249
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initscripts
Version: 2.88dsf-43
Severity: normal
Dear Maintainer,
Normally, the mount-functions.sh mounts /run, /tmp, etc as tmpfs
filesystems. To signal this fact to the other bootscripts, it creates a
".tmpfs" file inside.
However, when the mounting fails, and the corresponding filesystem has
thus _not_ been turned into a tmpfs, the .tmpfs file is still created.
In my case, this happened inside an lxc container. Because the mounting
capability was dropped for the container, mounting /run failed. However,
since .tmpfs was still created, the bootclean logic did not run, making
my container run with a dirty /run, causing all kinds of problems.
I looked at making a patch that made domount return a failure if the
(re)mount failed and made the mount_* functions only create .tmpfs files
if the mount succeeded.
However, I ran into two problems:
- Currently, .tmpfs is also touched when the filesystem is only
remounted, which probably doesn't make sense in the first place?
- When there is already a mountpoint (e.g., /run mounted by initramfs),
no mounting happens. I'd say this should make domount return failure
and prevent creating .tmpfs.
However, looking at the initramfs code, it seems that it mounts a
tmpfs on /run but does _not_ create the .tmpfs file, so if
mount_run doesn't create it, it will never be created in the
initramfs case...
I wonder if it makes sense to actively check if /run (etc.) is a
mountpoint and look into /proc/mounts (or whatever is the best way for
this) to see if it is a tmpfs? Then this could just happen after the
mount and it doesn't matter if the mount failed or succeeded, or if the
filesystem was already a tmpfs to begin with.
Does that make sense?
Gr.
Matthijs
-- System Information:
Debian Release: 7.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages initscripts depends on:
ii coreutils 8.13-3.5
ii debianutils 4.3.2
ii libc6 2.17-92
ii lsb-base 4.1+Debian8+deb7u1
ii mount 2.20.1-5.3
ii sysv-rc 2.88dsf-41
ii sysvinit-utils 2.88dsf-41
Versions of packages initscripts recommends:
ii e2fsprogs 1.42.5-1.1
ii psmisc 22.19-1+deb7u1
initscripts suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 3.15-3
Done: Mark Hindley <[email protected]>
We believe that the bug you reported is fixed in the latest version of
sysvinit, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mark Hindley <[email protected]> (supplier of updated sysvinit package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 08 Oct 2025 09:59:57 +0100
Source: sysvinit
Architecture: source
Version: 3.15-3
Distribution: experimental
Urgency: medium
Maintainer: Debian sysvinit maintainers
<[email protected]>
Changed-By: Mark Hindley <[email protected]>
Closes: 538257 686895 719249 1116288
Changes:
sysvinit (3.15-3) experimental; urgency=medium
.
* Update inittab on new installations to use ids consistent with
inittab(5). (Closes: #538257)
* Deprecate forcefsck. (Closes: #686895)
* d/control: add Depends login (no longer Essential). (Closes: #1116288)
* Only create .tmpfs if mount has been successful. (Closes: #719249)
* Remove all obsolete commented AC checking code. See #326647 and
related for discussion.
* d/copyright: remove old FSF address (lintian).
* d/copyright: update upstream contact and URL.
Checksums-Sha1:
b868b497a9c2b0a7d31a004e80866f7eee51d071 2382 sysvinit_3.15-3.dsc
7b83e988ac59e8631804d5f920b8a593866d019b 122744 sysvinit_3.15-3.debian.tar.xz
9dee39880a2acb26b44f69c84ee7c239cd989eb7 8072 sysvinit_3.15-3_amd64.buildinfo
Checksums-Sha256:
d71333f0250c7803f6920d6e4cac5701236d5cf3b1cef7b8360cfe23b72557fe 2382
sysvinit_3.15-3.dsc
d74fd5cf85443ee343a39301d565d73f2f58a1874aa52a69723818c960b672ae 122744
sysvinit_3.15-3.debian.tar.xz
9d76baa3505913bc96c98a16c80b1831636bd99da21e47d79f1115a4ea32bd18 8072
sysvinit_3.15-3_amd64.buildinfo
Files:
18ebd62deb5fb1fce7a4987188988385 2382 admin optional sysvinit_3.15-3.dsc
856146bb17e24cadba868c8c8d71e64f 122744 admin optional
sysvinit_3.15-3.debian.tar.xz
56580e9d9227bcf3688d236eae2bad76 8072 admin optional
sysvinit_3.15-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEUGwVpCsK9aCoVCPu0opFvzKH1kkFAmjmNm0ACgkQ0opFvzKH
1kmLNBAAh0sZpXMddWvl8S+lcLSq3La1K2pAe5y61NNX1sbnhxvi9/gieG8IHSED
WG1WRsgs4Y+CM02Nhjsv/G1CoZeRkfYDWKXIJE+ZBpKIBoCSsxVJa4/Ahs9xW3mI
251oGHD5q6HlWeMrnLg4i4K8CZK+TapnjcMnRc4xbiJiScGTOkpM8uE8OmYv1LE1
8vv9P6xIiEqxYJOLVgck3d82w2TKyJ4fPTeQNJqRc9tJU77txEklPrAOHEeGcBqG
VBTZxGijglKsyPJytO4QZdHhJLrg8UvkTg15wU/SBW56kOPhFOF41RdAyvWNJ3B6
QI8Js6cNBIi3Ms1w0fABv54vqUr0sPAY98wNibL1KHh1rRkq9+K2FpExFBpmSmRi
y5JgY+rbKBoRQxqgwKaZ+ebTXGCbR/mcJ1L7mND0muby2MIFp1c7aYFWc4ItM3Ip
X0ZKaL75f7A8xhxcqkJI5HZ2d8fUula8nH2G1W8+DdCYBOPMknIHblx/sutQB+w0
DrWFKFLNDsXi9kw6nxlG+0LBoH7ClP3IhQfz6U4PsscqycM0Npaet3YJ+YsIZVEY
X8V+att1jKpfVfHQXZ7o2xUkyTKnlpUM7E0FOjvGn/0a+a0jl27Iwh7tLQGiwLZJ
fmLuc++qiS3OLloUuyoE08XPcOHg7iOe9HbJuwLUnAaDpcpv0uU=
=tU8x
-----END PGP SIGNATURE-----
pgpM0xjcFhYpq.pgp
Description: PGP signature
--- End Message ---
