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.

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

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

Conversation

cpaelzer
Copy link

As discussed in #18 this is a suggestion to fix the ordering issue on shutdown.

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
Copy link
Author

Hrm, the mirror seems to be out of date.
This is based on git://sourceware.org/git/lvm2.git master which seems to be the main repo.
But for that git there isn't a PR interface, yet https://github.com/lvmteam/lvm2.git is slightly out of date.

Let me know if you want me to rebase to the master of https://github.com/lvmteam/lvm2.git or instead submit this somewhere else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant