Re: [systemd-devel] Infinite loop at startup on var fsck failure
On Tue, Mar 31, 2020 at 03:32:04PM +0200, Lennart Poettering wrote: > On Mo, 24.02.20 16:01, Vito Caputo (vcap...@pengaru.com) wrote: > > > Hello list, > > > > Today I experienced an unclean shutdown due to battery dying unexpectedly, > > and it left my /var in a state requiring a manual fsck to repair errors. > > > > The normal startup process failed and dropped me to a rescue shell after > > asking for my root password. But I was unable to immediately run fsck > > manually, because systemd was endlessly trying to fsck /var. > > Hmm, looks like a bug. It shouldn't keep retrying. Something mst > have pulled in the unit over and over again... > > Any chance you can reproduce this with current systemd, and maybe > provide logs and put them into a github issue? > > Or do you have logs from the case when this happened around? > No logs, since it was /var that needed the fsck, nothing persisted from the rescue and I was in a cafe at the time trying to boot my laptop to work on something else. Regrettably I didn't take the time to copy the volatile journals somewhere else, I was too annoyed at the time. What I'm hearing is that this isn't a known fixed issue, which is concerning. If I get a chance I'll poke at a repro, but it's pretty low on the priority list at the moment. Thanks for the response! Regards, Vito Caputo ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Infinite loop at startup on var fsck failure
On Mo, 24.02.20 16:01, Vito Caputo (vcap...@pengaru.com) wrote: > Hello list, > > Today I experienced an unclean shutdown due to battery dying unexpectedly, > and it left my /var in a state requiring a manual fsck to repair errors. > > The normal startup process failed and dropped me to a rescue shell after > asking for my root password. But I was unable to immediately run fsck > manually, because systemd was endlessly trying to fsck /var. Hmm, looks like a bug. It shouldn't keep retrying. Something mst have pulled in the unit over and over again... Any chance you can reproduce this with current systemd, and maybe provide logs and put them into a github issue? Or do you have logs from the case when this happened around? Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Infinite loop at startup on var fsck failure
Hello list, Today I experienced an unclean shutdown due to battery dying unexpectedly, and it left my /var in a state requiring a manual fsck to repair errors. The normal startup process failed and dropped me to a rescue shell after asking for my root password. But I was unable to immediately run fsck manually, because systemd was endlessly trying to fsck /var. Stopping, disabling, masking, none of those obvious options to prevent 'systemd-fsck@dev-mapper-ssd\x2var.service' from starting again in this loop worked, and I don't recall seeing any guidance in the journal on what was the appropriate course of action. Eventually I resorted to `systemctl emergency` which seemed to get things quieted down enough for me to run the fsck manually. All's well that ends well, but what an *awful* user experience. Is this really how things are supposed to play out when a fsck on something like /var fails? I was very much left in the dark at a root shell with systemd pointlessly spinning its wheels hopelessly running the same fsck repeatedly. It's possible this is already better in a newer systemd release, but I just wanted to document this experience in case it's an area that still needs improvement. This is on an old release (v232) in Debian 9.11 amd64. Regards, Vito Caputo ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
