[Cluster-devel] [PATCH 5/5] gfs2: dlm based recovery coordination

[Steven Whitehouse <swhiteho@redhat.com>]

Hi,

On Thu, 2012-01-05 at 10:46 -0600, David Teigland wrote:
> This new method of managing recovery is an alternative to
> the previous approach of using the userland gfs_controld.
> 
> - use dlm slot numbers to assign journal id's
> - use dlm recovery callbacks to initiate journal recovery
> - use a dlm lock to determine the first node to mount fs
> - use a dlm lock to track journals that need recovery
> 
> Signed-off-by: David Teigland <teigland@redhat.com>
> ---
>  fs/gfs2/glock.c             |    2 +-
>  fs/gfs2/glock.h             |    7 +-
>  fs/gfs2/incore.h            |   58 +++-
>  fs/gfs2/lock_dlm.c          |  993 ++++++++++++++++++++++++++++++++++++++++++-
>  fs/gfs2/main.c              |   10 +
>  fs/gfs2/ops_fstype.c        |   29 +-
>  fs/gfs2/recovery.c          |    4 +
>  fs/gfs2/sys.c               |   33 +-
>  fs/gfs2/sys.h               |    2 +
>  include/linux/gfs2_ondisk.h |    2 +
>  10 files changed, 1098 insertions(+), 42 deletions(-)
> 

I've just been looking at this again, and a question springs to mind...
how does this deal with nodes which are read-only or spectator mounts?
In the old system we used to propagate that information to gfs_controld
but I've not spotted anything similar in the patch so far, so I'm
wondering whether it needs to know that information or not,

Steve.