From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22671 invoked by alias); 28 Mar 2006 05:30:20 -0000 Received: (qmail 22658 invoked by uid 9475); 28 Mar 2006 05:30:20 -0000 Date: Tue, 28 Mar 2006 05:30:00 -0000 Message-ID: <20060328053020.22656.qmail@sourceware.org> From: bmarzins@sourceware.org To: cluster-cvs@sources.redhat.com Subject: cluster/gnbd/client gnbd_monitor.c Mailing-List: contact cluster-cvs-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: cluster-cvs-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00436.txt.bz2 List-Id: CVSROOT: /cvs/cluster Module name: cluster Changes by: bmarzins@sourceware.org 2006-03-28 05:30:19 Modified files: gnbd/client : gnbd_monitor.c Log message: If it took too long for an uncached gnbd recvd process to stop after the server was fenced, gnbd_monitor would mistakenly think that the old dying process was a new starting process. Because of this, the client would not auto-restart the gnbd device when the server started back up. This is now fixed. Now, gnbd_monitor will not move a device from the reset state to the restartable state unless the old recvd process has stopped. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gnbd/client/gnbd_monitor.c.diff?cvsroot=cluster&r1=1.9&r2=1.10