Bug#1057417: systemd tmpfiles seems to delete lost+found again

Axel Scheepers axel.scheepers76 at gmail.com
Tue Dec 5 11:48:05 GMT 2023


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 <biebl at 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20231205/59bddaa5/attachment.htm>


More information about the Pkg-systemd-maintainers mailing list