cluster/cmirror-kernel/src dm-cmirror-client.c ...

[jbrassow@sourceware.org]

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL4
Changes by:	jbrassow@sourceware.org	2006-06-02 22:04:51

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

Log message:
	- Fix for bugs: 193596 193706
	- Potential fix for: 193736 193902 (these fix message output change only)
	
	193596: node recovery can cause cluster mirror copying to halt
	Before we had the ability to detect whether or not another member node was recovering, I made sure that only the server would recover the mirror.  However, this meant that other nodes would recieve the signal not to recover.  So, in this case, when the server failed/left, recovery would stop.
	
	Now that we have the ability to detect remote recovery, I have remove the stipulation that only the server can recover.  This has fixed the problem for me.
	
	193706: cluster mirror copy starts over when node is recovered
	This was a problem were I was making the complete_resync_work function handle what should have been in the clear_region function for recovery scenarios.  The result was that although the clear_region was happening, that bitmap was not properly being written.
	
	193736: deactivating an active cmirror will can cause 1000s of d-m messages
	Yeah, I think I put that in there for my own debugging...
	Changed DMERR -> DMINFO.
	
	193902: mirror volume removal causes "A node has left the cluster" message
	Proposing "A cluster mirror log member has left."

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/cmirror-kernel/src/dm-cmirror-client.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.1.2.13&r2=1.1.2.14
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.6&r2=1.1.2.7