From: wcheng@sourceware.org <wcheng@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs-kernel/src/gfs lm.c
Date: 27 Nov 2006 20:22:34 -0000 [thread overview]
Message-ID: <20061127202234.28332.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: wcheng at sourceware.org 2006-11-27 20:22:34
Modified files:
gfs-kernel/src/gfs: lm.c
Log message:
bugzilla : 217374 - temporarily disable GFS1 withdraw until bz215962 is ready.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/lm.c.diff?cvsroot=cluster&r1=1.18&r2=1.19
--- cluster/gfs-kernel/src/gfs/lm.c 2006/09/20 18:48:56 1.18
+++ cluster/gfs-kernel/src/gfs/lm.c 2006/11/27 20:22:34 1.19
@@ -104,10 +104,20 @@
vprintk(fmt, args);
va_end(args);
+#if !defined(BZ_215962)
+ /*
+ * Temporarily disable GFS1 withdraw function until bz215962
+ * is ready.
+ *
+ * A side note: BUG() does stack dump too.
+ */
+ printk("GFS: fsid=%s: about to withdraw from the cluster\n",
+ sdp->sd_fsname);
+ BUG();
+#else
printk("about to withdraw from the cluster\n");
BUG_ON(sdp->sd_args.ar_debug);
-
printk("waiting for outstanding I/O\n");
/* FIXME: suspend dm device so oustanding bio's complete
@@ -117,6 +127,7 @@
gfs2_withdraw_lockproto(&sdp->sd_lockstruct);
printk("withdrawn\n");
dump_stack();
+#endif
return -1;
}
next reply other threads:[~2006-11-27 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 20:22 wcheng [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-05 22:38 [Cluster-devel] cluster/gfs-kernel/src/gfs lm.c teigland
2006-12-05 22:38 teigland
2006-12-05 22:38 teigland
2006-11-27 17:42 wcheng
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=20061127202234.28332.qmail@sourceware.org \
--to=wcheng@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.