From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/group/gfs_controld plock.c
Date: 16 Aug 2006 19:30:38 -0000 [thread overview]
Message-ID: <20060816193038.32446.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: teigland at sourceware.org 2006-08-16 19:30:37
Modified files:
group/gfs_controld: plock.c
Log message:
after unlinking a ckpt, don't try to close it if we don't have it open,
(no big problem, the close would just fail) and go back to syslogging
ckpt close errors
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/gfs_controld/plock.c.diff?cvsroot=cluster&r1=1.15&r2=1.16
--- cluster/group/gfs_controld/plock.c 2006/08/16 17:05:24 1.15
+++ cluster/group/gfs_controld/plock.c 2006/08/16 19:30:36 1.16
@@ -1081,6 +1081,9 @@
s.numberOfSections, s.memoryUsed);
out_close:
+ if (!h)
+ goto out;
+
rv = saCkptCheckpointClose(h);
if (rv == SA_AIS_ERR_TRY_AGAIN) {
log_group(mg, "unlink ckpt close retry");
@@ -1088,11 +1091,12 @@
goto out_close;
}
if (rv != SA_AIS_OK) {
- /* should this be log_error */
- log_group(mg, "unlink ckpt close error %d", rv);
- ret = -1;
+ log_error("unlink ckpt %llx close err %d %s", h, rv, mg->name);
+ /* should we return an error here and possibly cause
+ store_plocks() to fail on this? */
+ /* ret = -1; */
}
-
+ out:
mg->cp_handle = 0;
return ret;
}
next reply other threads:[~2006-08-16 19:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 19:30 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-30 16:20 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 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=20060816193038.32446.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.