On 2015-04-27 Michael Biebl <bi...@debian.org> wrote: > Am 27.04.2015 um 19:15 schrieb Andreas Metzler: >> On 2015-04-27 Michael Biebl <bi...@debian.org> wrote: [...] >>> Or maybe, have you tmpfs-on-tmp enabled?
>> thanks for the help, that is exactly what seems to have happened: [...] >> ametzler@argenau:~$ mount | grep ' /tmp' >> tmpfs on /tmp type tmpfs (rw) >> ametzler@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@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): [...] >> /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? Hello, Yes, unless the logfile has suddenly increased in verbosity ATM. The "Mounting Temporary Directory..." message started appearing after that upgrade. > Can you verify that by downgrading the packages from snapshot.debian.org? I am reluctant to do so, since this is my main system and downgrades are generally not handled (that well) in package maintainer-scripts. > 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)? They have been setup (manually) in fstab: /tmp /chroots/wheezy/tmp none bind,auto 0 0 > Can you attach a systemd-analyze dump, please. Sure. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
systemd-analyze_dump.xz
Description: application/xz
