From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31909 invoked by alias); 19 Dec 2006 20:06:45 -0000 Received: (qmail 31884 invoked by uid 9453); 19 Dec 2006 20:06:44 -0000 Date: Tue, 19 Dec 2006 20:06:00 -0000 Message-ID: <20061219200644.31883.qmail@sourceware.org> From: teigland@sourceware.org To: cluster-cvs@sources.redhat.com Subject: cluster/gfs-kernel/src/gfs ops_fstype.c Mailing-List: contact cluster-cvs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: cluster-cvs-owner@sourceware.org X-SW-Source: 2006-q4/txt/msg00817.txt.bz2 CVSROOT: /cvs/cluster Module name: cluster Changes by: teigland@sourceware.org 2006-12-19 20:06:44 Modified files: gfs-kernel/src/gfs: ops_fstype.c Log message: When the first mounter is recovering all the journals, it should use TRY on the journal locks. There's one rare case where other mounters will exist who hold journal locks that we don't want to block on. That's when the other mounters are readonly, haven't been able to recover the fs after a node failure, and the next rw mounter is told to do first mounter recovery. The journals of these readonly nodes can be skipped when the pseudo-first mounter is going through all journals. Changed this a long time ago but never checked it in. bz 218551 Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&r1=1.28&r2=1.29