Red Hat Bugzilla – Bug 1466040
systemd sometimes reboots without umounting filesystems
Last modified: 2018-06-20 22:25:30 EDT
Description of problem:
systemd seems to sometimes reboot the system forcefully even if filesystems are not umounted, probably due to files being still opened in them.
This is difficult to debug, but the behaviour is as such:
* boot failures if grubby was run recently ( due to it not flushing buffers / metadata to disk => https://bugzilla.redhat.com/show_bug.cgi?id=1464611 )
* Running "umount /boot" before rebooting fixes the above issue
Possibly other data loss in other filesystems could occur.
Version-Release number of selected component (if applicable):
Difficult, probably requires specific environments. However, there are sporadic reports of this happening:
system reboots without unmounting filesystems
Filesystems are closed or at least buffers are
I have no idea how to list open files to some log so late in the reboot cycle, so I'd appreciate any insight on how to do that.
(In reply to François Cami from comment #0)
> Additional info:
> I have no idea how to list open files to some log so late in the reboot
> cycle, so I'd appreciate any insight on how to do that.
Please refer to https://freedesktop.org/wiki/Software/systemd/Debugging/ section "Shutdown Completes Eventually". But please edit the script and add invocation of "lsof" (note that lsof is not installed by default) to it. Once you reproduce please update the bugzilla and upload the log file.