Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix shutdown ordering to go after mounts are let go #19

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix shutdown ordering to go after mounts are let go #19

wants to merge 1 commit into from

Commits on Jun 19, 2019

  1. systemd: fix shutdown ordering to be after FS umount 

    Currently on shutdown blk_availability will start almost as early
as possible and invoke blkdeactivate.
This can make devices and the filesystems on them unavailable that will
still be needed by other parts of the shutdown.

Usually such services needing the local filesystem will have declared
  After=local-fs.target
And expect to be shut down before things are unmounted.

But blkdeactivate might unmount things before all of that.
To guarantee no devices / filesystems going away too early let us
declare for blk_availability:
  Before=local-fs.target

On shutdown that ensures that blkdeactivate will only be ordered after
local-fs.target which seems what users would expect.

Fixes: lvmteam#18

Signed-off-by: Christian Ehrhardt <[email protected]>
    @cpaelzer
    cpaelzer committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    741ee6e View commit details
    Browse the repository at this point in the history