You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While looking into #2283 I noticed some possible umount races on shutdown for the the ostree bindmounts. This shows up in in the journal logs for the (automatically mirrored) mount units:
systemd[1]: Unmounting /etc...
systemd[1]: Unmounting /var...
umount[1635]: umount: /etc: target is busy.
umount[1639]: umount: /var: target is busy.
systemd[1]: etc.mount: Mount process exited, code=exited status=32
systemd[1]: Failed unmounting /etc.
systemd[1]: var.mount: Mount process exited, code=exited status=32
systemd[1]: Failed unmounting /var.
The text was updated successfully, but these errors were encountered:
It looks like the main culprit here may be systemd itself, in particular journald . The logs above are on a system with systemd v239.
On a system with a newer systemd version (v248) I'm not seeing those races/failures. The bindmounts instead are cleaned at the bottom through systemd-shutdown. systemd/systemd#12230 is possibly the one that fixed it.
While looking into #2283 I noticed some possible umount races on shutdown for the the ostree bindmounts. This shows up in in the journal logs for the (automatically mirrored) mount units:
The text was updated successfully, but these errors were encountered: