From owner-freebsd-current@FreeBSD.ORG Tue Apr 24 11:53:42 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F94C16A480; Tue, 24 Apr 2007 11:53:42 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.freenix.fr (keltia.freenix.org [82.230.37.243]) by mx1.freebsd.org (Postfix) with ESMTP id D3BEF13C44B; Tue, 24 Apr 2007 11:53:41 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from localhost (localhost [127.0.0.1]) by keltia.freenix.fr (Postfix/TLS) with ESMTP id 8E1533939F; Tue, 24 Apr 2007 13:53:40 +0200 (CEST) Received: from keltia.freenix.fr ([127.0.0.1]) by localhost (keltia.freenix.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02150-05; Tue, 24 Apr 2007 13:53:40 +0200 (CEST) Received: by keltia.freenix.fr (Postfix/TLS, from userid 101) id 31C1639393; Tue, 24 Apr 2007 13:53:40 +0200 (CEST) Date: Tue, 24 Apr 2007 13:53:40 +0200 From: Ollivier Robert To: freebsd-current@freebsd.org, current@freebsd.org, William Josephson Message-ID: <20070424115340.GA2172@keltia.freenix.fr> References: <20070424051420.GA84831@mero.morphisms.net> <200704241554.12605.doconnor@gsoft.com.au> <20070424084409.GA98777@keltia.freenix.fr> <200704241942.40874.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200704241942.40874.doconnor@gsoft.com.au> X-Operating-System: MacOS X / Macbook Pro - FreeBSD 6.2 / Dell D820 SMP User-Agent: Mutt/1.5.14 (2007-02-12) X-Virus-Scanned: amavisd-new at keltia.freenix.fr Cc: Subject: Re: ATA FLUSHCACHE 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, 24 Apr 2007 11:53:42 -0000 According to Daniel O'Connor: > Hmm, it is a non fatal error for gjournal, I'm kind of surprised it's a > fatal one for ZFS.. It is not a fatal one for ZFS per se. If I use ZFS in a configuration that does not require writing on two disks (a gconcat-like configuration), it works and FLUSHCACHE timeouts are not fatal. As soon as I try to get it working in a more disk-intensive (raidz in that case) way, it blows up with a panic. It seems to point to a flaw in the ata driver which may not be managing semaphores/mutex correctly or maybe in the way it uses UMA zones (the panic starts there). ZFS is only a very reproductible way of triggering the problem. > If the cache flush really failed (eg due to a stuffed disk) then there > really is a problem, but IMO it is likely this is going to be caught by > a read or a write operation very soon. Yes. > If it is a transient error then panicing seems to be about the worse > response :) Agreed. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Darwin sidhe.keltia.net Kernel Version 8.8.2: Thu Sep 28 20:43:26 PDT 2006 i386