From owner-freebsd-geom@FreeBSD.ORG Wed Jan 19 18:26:44 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 E8FF716A4CE for ; Wed, 19 Jan 2005 18:26:44 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C9C643D5F for ; Wed, 19 Jan 2005 18:26:44 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id B3BD6ACB34; Wed, 19 Jan 2005 19:26:41 +0100 (CET) Date: Wed, 19 Jan 2005 19:26:41 +0100 From: Pawel Jakub Dawidek To: Brian McCann Message-ID: <20050119182641.GO795@darkness.comp.waw.pl> References: <2b5f066d05011910056e7a69e1@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Q6K/XF9FZiHksLwH" Content-Disposition: inline In-Reply-To: <2b5f066d05011910056e7a69e1@mail.gmail.com> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: freebsd-geom@freebsd.org Subject: Re: ggatec reporting false info / not exiting correct? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list 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:26:45 -0000 --Q6K/XF9FZiHksLwH Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 19, 2005 at 01:05:22PM -0500, Brian McCann wrote: +> 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. And if you run: # ggatec attach -u 0 ... Does it work again? It should. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --Q6K/XF9FZiHksLwH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFB7qZhForvXbEpPzQRAkk9AKCb0NnnsLEOsfhKb+z4WyTc1HYMiQCffkwT 0LIyNtgkA28CbRHPQMNEVLU= =5aqC -----END PGP SIGNATURE----- --Q6K/XF9FZiHksLwH--