cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/group/gfs_controld plock.c
Date: 30 Nov 2007 16:20:56 -0000	[thread overview]
Message-ID: <20071130162056.24352.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	teigland at sourceware.org	2007-11-30 16:20:56

Modified files:
	group/gfs_controld: plock.c 

Log message:
	change some log messages

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/gfs_controld/plock.c.diff?cvsroot=cluster&r1=1.35&r2=1.36

--- cluster/group/gfs_controld/plock.c	2007/11/29 21:27:58	1.35
+++ cluster/group/gfs_controld/plock.c	2007/11/30 16:20:55	1.36
@@ -971,6 +971,9 @@
 	   - A sends drop, B sends plock, receive drop, receive plock.
 	   This is addressed above.
 
+	   - A sends drop, B sends plock, receive drop, B reads plock
+	   and sends own, receive plock, on B we find owner of -1.
+
 	   - A sends drop, B sends two plocks, receive drop, receive plocks.
 	   Receiving the first plock is the previous case, receiving the
 	   second plock will find r with owner of -1.
@@ -983,23 +986,29 @@
 	   last case below; receiving a plock from ourself and finding
 	   we're the owner of r. */
 
-	/* may want to supress this if some of them are common enough */
-	if (r->owner)
-		log_error("receive_plock from %d r %llx owner %d", from,
-			  (unsigned long long)info.number, r->owner);
-
 	if (!r->owner) {
 		__receive_plock(mg, &info, from, r);
 
 	} else if (r->owner == -1) {
+		log_debug("receive_plock from %d r %llx owner %d", from,
+			  (unsigned long long)info.number, r->owner);
+
 		if (from == our_nodeid)
 			save_pending_plock(mg, r, &info);
 
 	} else if (r->owner != our_nodeid) {
+		/* might happen, if frequent change to log_debug */
+		log_error("receive_plock from %d r %llx owner %d", from,
+			  (unsigned long long)info.number, r->owner);
+
 		if (from == our_nodeid)
 			save_pending_plock(mg, r, &info);
 
 	} else if (r->owner == our_nodeid) {
+		/* might happen, if frequent change to log_debug */
+		log_error("receive_plock from %d r %llx owner %d", from,
+			  (unsigned long long)info.number, r->owner);
+
 		if (from == our_nodeid)
 			__receive_plock(mg, &info, from, r);
 	}



             reply	other threads:[~2007-11-30 16:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 16:20 teigland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-21 20:21 [Cluster-devel] cluster/group/gfs_controld plock.c teigland
2008-01-21 20:19 teigland
2008-01-21 20:17 teigland
2007-11-29 21:27 teigland
2007-06-08 21:31 teigland
2007-06-08 21:30 teigland
2006-11-20 21:29 teigland
2006-11-20 21:29 teigland
2006-11-20 21:28 teigland
2006-11-20 18:13 teigland
2006-11-20 18:12 teigland
2006-11-20 18:10 teigland
2006-11-03 15:33 teigland
2006-10-09 21:51 teigland
2006-08-17 19:39 teigland
2006-08-16 19:30 teigland
2006-08-16 17:05 teigland
2006-08-15 22:21 rpeterso
2006-08-14 20:15 teigland
2006-08-08 19:37 teigland
2006-08-08 18:43 teigland
2006-08-02 19:23 teigland

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=20071130162056.24352.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).