Re: [Cluster-devel] [DLM PATCH] dlm_controld: handle the case of network transient disconnection

On Thu, May 12, 2016 at 05:16:08PM +0800, Eric Ren wrote: > DLM would be stuck in "need fencing" state, although cluster can > regain quorum very quickly after a network transient disconnection. > > It's possible that this process happens within one monoclock. It > means

[Cluster-devel] [PATCH v2] gfs2: Switch to generic xattr handlers

From: Al Viro Al, this is based on your gfs2-untested branch, to replace the following two commits on work.xattr: posix acls: Export xattr_handler functions gfs2: Switch to generic xattr handlers Thanks, Andreas -- Switch to the generic xattr handlers and take

Re: [Cluster-devel] [DLM PATCH] dlm_controld: handle the case of network transient disconnection

Hi David, Thanks very very much for explaining this to me in such nice way;-) On 05/13/2016 12:51 AM, David Teigland wrote: T = time in seconds, A,B,C = cluster nodes. At T=1 A,B,C become members and have quorum. At T=10 a partition creates A,B | C. At T=11 it merges and creates A,B,C. At

[Cluster-devel] [DLM PATCH] dlm_controld: handle the case of network transient disconnection

DLM would be stuck in "need fencing" state, although cluster can regain quorum very quickly after a network transient disconnection. It's possible that this process happens within one monoclock. It means "cluster_quorate_monotime" can eqaul "node->daemon_rem_time". We now skip this chance of