From: jbrassow@sourceware.org <jbrassow@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cmirror-kernel/src dm-cmirror-server.c
Date: 10 Apr 2007 18:09:10 -0000 [thread overview]
Message-ID: <20070410180910.32240.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: jbrassow at sourceware.org 2007-04-10 19:09:09
Modified files:
cmirror-kernel/src: dm-cmirror-server.c
Log message:
Remove an overzealous BUG statement.
Comments inlined
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cmirror-kernel/src/dm-cmirror-server.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.1.2.31&r2=1.1.2.32
--- cluster/cmirror-kernel/src/Attic/dm-cmirror-server.c 2007/04/10 07:12:24 1.1.2.31
+++ cluster/cmirror-kernel/src/Attic/dm-cmirror-server.c 2007/04/10 18:09:09 1.1.2.32
@@ -708,7 +708,18 @@
if (!ru) {
DMERR("Unable to find region to be marked out-of-sync: %Lu/%s/%u",
lr->u.lr_region, lc->uuid + (strlen(lc->uuid) - 8), who);
- BUG();
+ /*
+ * This is a valid case, when the following happens:
+ * 1) a region is recovering and has waiting writes
+ * 2) recovery fails and calls complete_resync_work (w/ failure)
+ * 2.1) RU is removed from our list
+ * 3) waiting writes are released
+ * 3.1) writes do not mark, because b/c region state != RH_CLEAN
+ * 4) write fails and calls complete_resync_work (w/ failure)
+ * 5) boom, we are here.
+ *
+ * Not a bug to be here
+ */
} else if (ru->ru_rw == RU_RECOVER) {
if (lr->u.lr_region != lc->recovering_region) {
DMERR("Recovering region mismatch from node %u: (%Lu/%Lu)",
next reply other threads:[~2007-04-10 18:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 18:09 jbrassow [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-26 18:46 [Cluster-devel] cluster/cmirror-kernel/src dm-cmirror-server.c jbrassow
2007-04-17 19:49 jbrassow
2007-04-10 18:10 jbrassow
2007-04-04 21:36 jbrassow
2007-04-04 21:35 jbrassow
2006-07-22 22:51 jbrassow
2006-07-22 22:50 jbrassow
2006-07-22 22:49 jbrassow
2006-07-19 14:40 jbrassow
2006-07-19 14:39 jbrassow
2006-07-19 14:38 jbrassow
2006-06-27 20:26 jbrassow
2006-06-27 20:25 jbrassow
2006-06-21 21:21 jbrassow
2006-06-21 21:09 jbrassow
2006-06-14 22:14 jbrassow
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=20070410180910.32240.qmail@sourceware.org \
--to=jbrassow@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).