diff options
author | Bob Peterson <rpeterso@redhat.com> | 2019-06-13 21:28:45 +0300 |
---|---|---|
committer | Bob Peterson <rpeterso@redhat.com> | 2020-02-20 20:01:36 +0300 |
commit | a72d2401f54b7db41c77ab971238a06eafe929fb (patch) | |
tree | f1055bffda071498f6da9577c4b12aabc57fa299 /fs/gfs2/lock_dlm.c | |
parent | 0d91061a372671aec1af729686ad9241a59fc328 (diff) | |
download | linux-a72d2401f54b7db41c77ab971238a06eafe929fb.tar.xz |
gfs2: Allow some glocks to be used during withdraw
We need to allow some glocks to be enqueued, dequeued, promoted, and demoted
when we're withdrawn. For example, to maintain metadata integrity, we should
disallow the use of inode and rgrp glocks when withdrawn. Other glocks, like
iopen or the transaction glocks may be safely used because none of their
metadata goes through the journal. So in general, we should disallow all
glocks with an address space, and allow all the others. One exception is:
we need to allow our active journal to be demoted so others may recover it.
Allowing glocks after withdraw gives us the ability to take appropriate
action (in a following patch) to have our journal properly replayed by
another node rather than just abandoning the current transactions and
pretending nothing bad happened, leaving the other nodes free to modify
the blocks we had in our journal, which may result in file system
corruption.
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
Diffstat (limited to 'fs/gfs2/lock_dlm.c')
0 files changed, 0 insertions, 0 deletions