All of lore.kernel.org
 help / color / mirror / Atom feed
From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs ops_fstype.c
Date: 19 Dec 2006 20:06:45 -0000	[thread overview]
Message-ID: <20061219200645.31891.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	teigland at 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

--- cluster/gfs-kernel/src/gfs/ops_fstype.c	2006/10/23 20:15:28	1.28
+++ cluster/gfs-kernel/src/gfs/ops_fstype.c	2006/12/19 20:06:44	1.29
@@ -436,7 +436,7 @@
 		for (x = 0; x < sdp->sd_journals; x++) {
 			error = gfs_recover_journal(sdp,
 						    x, sdp->sd_jindex + x,
-						    TRUE);
+						    FALSE);
 			if (error) {
 				printk("GFS: fsid=%s: error recovering journal %u: %d\n",
 				       sdp->sd_fsname, x, error);



             reply	other threads:[~2006-12-19 20:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 20:06 teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-19 14:25 [Cluster-devel] cluster/gfs-kernel/src/gfs ops_fstype.c rpeterso
2007-06-19 14:23 rpeterso
2006-12-19 20:07 teigland
2006-12-19 20:07 teigland
2006-08-10 14:52 rpeterso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061219200645.31891.qmail@sourceware.org \
    --to=teigland@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.