Bug#783509: systemd: /tmp purged on every reboot

[Michael Biebl]

Am 27.04.2015 um 19:15 schrieb Andreas Metzler:
> On 2015-04-27 Michael Biebl <biebl at debian.org> wrote:
>> Am 27.04.2015 um 18:15 schrieb Andreas Metzler:
>>> Package: systemd
>>> Version: 215-17
>>> Severity: normal
> 
>>> I am not sure for how long but I guess less than two months (jessie),
>>> systemd has started purging my /tmp on every reboot, although I have
>>> these settings:
> [...] 
>> Or maybe, have you tmpfs-on-tmp enabled?
> 
>> What's the output of systemctl status tmp.mount ?
> 
> Hello,
> 
> thanks for the help, that is exactly what seems to have happened:
> 
> --------------------------------------
> ametzler at argenau:~$ systemctl status tmp.mount
> ● tmp.mount - Temporary Directory
>    Loaded: loaded (/lib/systemd/system/tmp.mount; disabled)
>    Active: active (mounted) since Mon 2015-04-27 17:07:24 CEST; 1h 33min ago
>     Where: /tmp
>      What: tmpfs
>      Docs: man:hier(7)
>            http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
>   Process: 178 ExecMount=/bin/mount -n tmpfs /tmp -t tmpfs -o mode=1777,strictatime (code=exited, status=0/SUCCESS)
> 
> Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
> ametzler at argenau:~$ mount | grep ' /tmp'
> tmpfs on /tmp type tmpfs (rw)
> ametzler at argenau:~$ systemctl list-dependencies --reverse tmp.mount
> tmp.mount
> ● ├─chroots-amd64\x2djessie-tmp.mount
> ● ├─chroots-amd64\x2dwheezy-tmp.mount
> ● ├─chroots-etch-tmp.mount
> [...]
> ● └─chroots-wheezy-tmp.mount
> --------------------------------------
> 
> The reverse dependencies are just bind-mounts:
> ametzler at argenau:~$ grep /wheezy.*tmp /etc/fstab
> /tmp            /chroots/wheezy/tmp        none    bind,auto        0       0
> 
> It looks like this started on April 5 (journalctl history goes back to
> 2014):
> ametzler at argenau:~$ journalctl --since=2015-03-15 | grep tmp.mount
> Apr 05 15:20:55 argenau systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
> Apr 06 13:38:42 argenau systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
> [...]
> 
> /var/log/apt/history.log marks the upgrade to systemd 215-14 from -12 as
> triggering point:


So you're saying, with 215-12, tmp.mount was not automatically mounted?
Can you verify that by downgrading the packages from snapshot.debian.org?

Regarding those chroots-*-tmp.mount dependencies?

Who is creating those mounts? Maybe they didn't exist when you have -12
installed? How are they created? Are those bind mounts (via fstab)?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150427/a6ae8e01/attachment-0002.sig>