diff options
author | Alexander Aring <aahringo@redhat.com> | 2025-07-23 11:21:56 -0400 |
---|---|---|
committer | David Teigland <teigland@redhat.com> | 2025-08-12 11:37:21 -0500 |
commit | 6f4f4ca5caf73de5e86329547d4527b3e0c08488 (patch) | |
tree | 5843d3994f8173d87c853de702d0a3882fd33c21 /scripts/kernel-doc.py | |
parent | de7b4869b4ecf5790b0e7875c5522d43d7a61d79 (diff) |
dlm: add new flag DLM_RELEASE_RECOVER for dlm_lockspace_release
When dlm_lockspace_release() is passed DLM_RELEASE_RECOVER, it
tells the dlm to handle the release/leave as if the node had failed,
i.e. perform recovery steps for a failed node, like recover_slot().
When DLM_RELEASE_RECOVER is set:
- dlm_release_lockspace() includes RELEASE_RECOVER=1 in the OFFLINE
uevent sent to userspace.
- userspace/dlm_controld sends a message to all lockspace members
indicating that the subsequent node removal should be handled as
if the node had failed.
- when dlm_controld on all nodes receives the new message, it sets
the release_recover configfs entry to 1 for the node.
- when the dlm/kernel next performs recovery and removes the node,
it will see that release_recover has been set, and will perform
recovery steps for the node as if it had failed, e.g. the
recover_slot() callback is called to notify the fs.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
Diffstat (limited to 'scripts/kernel-doc.py')
0 files changed, 0 insertions, 0 deletions