| commit | 91c0dc93a1a6bbdd79707ed311e48b4397df177f | |
| author | David Teigland <teigland@redhat.com> | |
| Tue, 31 Oct 2006 17:56:01 +0000 (31 11:56 -0600) | ||
| committer | Steven Whitehouse <swhiteho@redhat.com> | |
| Thu, 30 Nov 2006 15:35:13 +0000 (30 10:35 -0500) | ||
| tree | ec78620714a49fc41244afb667404b0ff825b1a2 | treesnapshot (tar.gz zip) |
| parent | d4400156d415540086c34a06e5d233122d6bf56a | commitdiff |
[DLM] fix aborted recovery during node removal
Red Hat BZ 211914
With the new cluster infrastructure, dlm recovery for a node removal can
be aborted and restarted for a node addition. When this happens, the
restarted recovery isn't aware that it's doing recovery for the earlier
removal as well as the addition. So, it then skips the recovery steps
only required when nodes are removed. This can result in locks not being
purged for failed/removed nodes. The fix is to check for removed nodes
for which recovery has not been completed at the start of a new recovery
sequence.
Signed-off-by: David Teigland <teigland@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Red Hat BZ 211914
With the new cluster infrastructure, dlm recovery for a node removal can
be aborted and restarted for a node addition. When this happens, the
restarted recovery isn't aware that it's doing recovery for the earlier
removal as well as the addition. So, it then skips the recovery steps
only required when nodes are removed. This can result in locks not being
purged for failed/removed nodes. The fix is to check for removed nodes
for which recovery has not been completed at the start of a new recovery
sequence.
Signed-off-by: David Teigland <teigland@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
| fs/dlm/member.c | diffblobblamehistory | |
| fs/dlm/recoverd.c | diffblobblamehistory |