Yes you are right, I overlooked the existing exception, it is indeed probably the setup which causes it. I had rebooted the box previously and tested only the clearing service.
Kind regards, Axel Op di 5 dec. 2023 00:38 schreef Michael Biebl <bi...@debian.org>: > Am 04.12.23 um 23:09 schrieb Michael Biebl: > > The code to exclude lost+found appears to be still there: > > > https://github.com/systemd/systemd/blob/main/src/tmpfiles/tmpfiles.c#L720 > > > > Can you create a lost+found directory and then run > > SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --prefix /tmp > > > > ? > > I haven't really debugged this fully, but from a cursory glance it > appears that systemd-tmpfiles-setup.service is responsible for nuking > /tmp/lost+found > > systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev > doesn't preserve /tmp/lost+found which looks like a regression. >
