Control: tags -1 -upstream Control: close -1 On Tue, 5 Jul 2022 00:28:21 +0200 Michael Biebl <bi...@debian.org> wrote: > Control: tags -1 + upstream > On Fri, 8 Apr 2022 10:32:05 +0200 Laurent Bonnaud > <l.bonn...@laposte.net> wrote: > > On 4/7/22 18:41, Laurent Bonnaud wrote: > > > > > However I got it to work nevertheless by adding the "ro" mount option > > > in /etc/fstab for the root file system > > > > This "solves" the quotacheck problem, but unfortunately it has many other negative consequences, such as: > > > > Apr 08 05:01:29 hostname systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION > > Apr 08 05:01:29 hostname systemd[1]: swapfile.swap: Failed with result 'exit-code'. > > Apr 08 05:01:29 hostname systemd[1]: Failed to activate swap /swapfile. > > > > Apr 08 05:01:30 hostname systemd-tmpfiles[522]: rm_rf(/tmp): Read- only file system > > > > Apr 08 05:01:30 hostname systemd[539]: systemd-timesyncd.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Read- only file system > > Apr 08 05:01:30 hostname systemd[539]: systemd-timesyncd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timesyncd: Read- only file system > > > > Such this "solution" can only be used as a "one shot" trick followed by a proper reboot with a rw file system. > > > I assume you are using stable. > Can you please test, if you can still reproduce this with v250 from > bullseye-backports and if so, report this upstream at > https://github.com/systemd/systemd/issues
No answer nor upstream report in 2 years, closing. -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
