cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: jbrassow@sourceware.org <jbrassow@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/cmirror-kernel/src dm-cmirror-server.c
Date: 21 Jun 2006 21:21:02 -0000	[thread overview]
Message-ID: <20060621212102.13876.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL4U4
Changes by:	jbrassow at sourceware.org	2006-06-21 21:20:59

Modified files:
	cmirror-kernel/src: dm-cmirror-server.c 

Log message:
	- fix for bug 195610 (renaming a clustered mirror is broken)
	
	The problem is that LVM2/device-mapper calls the mirror constructor
	before calling the destructor.  This results in two copies of the
	log context to exist in the cluster mirror.
	
	I've added code to detect and handle this, but it should probably
	also be fixed in LVM2/device-mapper.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cmirror-kernel/src/dm-cmirror-server.c.diff?cvsroot=cluster&only_with_tag=RHEL4U4&r1=1.1.2.9&r2=1.1.2.9.2.1

--- cluster/cmirror-kernel/src/Attic/dm-cmirror-server.c	2006/06/14 22:14:55	1.1.2.9
+++ cluster/cmirror-kernel/src/Attic/dm-cmirror-server.c	2006/06/21 21:20:59	1.1.2.9.2.1
@@ -298,7 +298,6 @@
 	DMINFO("Disk Resume::");
 
 	debug_disk_write = 1;
-
 	memset(live_nodes, 0, sizeof(live_nodes));
 	for(i = 0; i < global_count; i++){
 		live_nodes[global_nodeids[i]/8] |= 1 << (global_nodeids[i]%8);
@@ -612,15 +611,19 @@
 
 
 static struct log_c *get_log_context(char *uuid){
-	struct log_c *lc;
+	struct log_c *lc, *r = NULL;
 
 	list_for_each_entry(lc, &log_list_head, log_list){
 		if(!strncmp(lc->uuid, uuid, MAX_NAME_LEN)){
-			return lc;
+			if (r)
+				DMERR("HEY!!! There are two matches for %s",
+				      lc->uuid + (strlen(lc->uuid) - 8));
+			else
+				r = lc;
 		}
 	}
 
-	return NULL;
+	return r;
 }
 
 



             reply	other threads:[~2006-06-21 21:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 21:21 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-10 18:09 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: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=20060621212102.13876.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).