From owner-freebsd-geom@FreeBSD.ORG Wed Jan 19 18:05:23 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0173516A4CE for ; Wed, 19 Jan 2005 18:05:23 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8612743D54 for ; Wed, 19 Jan 2005 18:05:22 +0000 (GMT) (envelope-from bjmccann@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so6775wra for ; Wed, 19 Jan 2005 10:05:22 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=qugnUgaYv3GoxA75uNjfwv28cVNCY6NlfMXFt434yTkiZXOk/TCftGD/GoKl2tvKBhOwHEV7j8iwTiwx6WpG/SC9/5jiT8WCJNQA7XQ7pUgLbxZQtr1Xk94BpUwMp17RNF2u5Rn9WThusoW7pWZCbrXTJYhNpvVfaOg61DNvBKQ= Received: by 10.54.22.53 with SMTP id 53mr29868wrv; Wed, 19 Jan 2005 10:05:22 -0800 (PST) Received: by 10.54.33.61 with HTTP; Wed, 19 Jan 2005 10:05:22 -0800 (PST) Message-ID: <2b5f066d05011910056e7a69e1@mail.gmail.com> Date: Wed, 19 Jan 2005 13:05:22 -0500 From: Brian McCann To: freebsd-geom@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: ggatec reporting false info / not exiting correct? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Brian McCann List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 18:05:23 -0000 Hi all. I'm working on getting gmirror to work over ggate connections..and it's working well...just trying to break it and make recovery situations. However, I've discovered what I believe to be a flaw in ggatec. I had PC1 running ggatec and PC2 running ggated. PC2 was exporting /dev/da1s1d. I had gmirror on PC1 setup with /dev/da1s1d and /dev/ggate0d. Was working great. I then simulated a failure in the network by killing ggated on PC2. gmirror saw the problem, marked the array accordingly. I then bought ggated back up on PC2. To my disappointment, ggatec had apparantly closed once there was a failure (thought it may have tried to reconnect at a given interval or something like NFS). However, when I ran "ggatec list", it showed "ggate0", and an ls of /dev showed a ggate0 as well....but no ggatec process was running. It's like when ggatec could not talk to ggated anymore it just gave up and quit, not cleaning up after itself at all...this can't be right...at least....I wouldn't think it to be right. Is it supposed to work like this (not cleaning up)? If so, I'm curious as to why. On a side note, it would be awesome if ggatec COULD have a background option...where if it can't contact the ggated host to wait and try again after a certain time. Thanks, --Brian