From owner-freebsd-current@FreeBSD.ORG Tue Mar 7 15:46:07 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A223516A420; Tue, 7 Mar 2006 15:46:07 +0000 (GMT) (envelope-from regnauld@x0.dk) Received: from x0.dk (x0.dk [62.242.165.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7FAD43D67; Tue, 7 Mar 2006 15:46:06 +0000 (GMT) (envelope-from regnauld@x0.dk) Received: from localhost (unknown [127.0.0.1]) by tetard.starbsd.org (Postfix) with ESMTP id DE3B6343F4; Tue, 7 Mar 2006 16:46:05 +0100 (CET) Received: from tetard.starbsd.org ([127.0.0.1]) by localhost (tetard.starbsd.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 26004-05; Tue, 7 Mar 2006 16:46:04 +0100 (CET) Received: by tetard.starbsd.org (Postfix, from userid 1001) id DE0FF34479; Tue, 7 Mar 2006 16:46:04 +0100 (CET) Date: Tue, 7 Mar 2006 16:46:04 +0100 From: Phil Regnauld To: Pawel Jakub Dawidek Message-ID: <20060307154604.GG25439@tetard.starbsd.org> References: <20060306222844.GC56506@garage.freebsd.pl> <20060307141519.GB25439@tetard.starbsd.org> <20060307151636.GB60850@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060307151636.GB60850@garage.freebsd.pl> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-STABLE i386 Organization: *BSD X-Virus-Scanned: amavisd-new at starbsd.org X-Mailman-Approved-At: Tue, 07 Mar 2006 15:47:58 +0000 Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: gmirror(8) and graid3(8) changes. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Mar 2006 15:46:07 -0000 On Tue, Mar 07, 2006 at 04:16:36PM +0100, Pawel Jakub Dawidek wrote: > +> > +> I've been experiencing lockups with gmirror, ATA/SATA on both > +> i386 and amd64, under severe I/O (very heavily loaded Postgres DB). > +> This has been on several different machines (remotely located, with > +> no possibility of breaking into the debugger). > +> > +> Do you think these patches are worth testing in my case ? > > Are you sure it was gmirror's fault? It doesn't happen if I use either underlying "raw" disk without gmirror. > It will be quite hard for gmirror > to hang machine so badly that we are not able to enter ddb... No, I meant, I couldn't access the box's DDB remotely as it was in a hosting center without access to a physical console, and I had to have someone restart it. > Anyway, I'd prefer to test those patches not in production environment > yet. It is a test machine, so I don't mind, was just curious if this could be related.