From owner-freebsd-stable@FreeBSD.ORG Tue Nov 30 02:10:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 654B510656A3; Tue, 30 Nov 2010 02:10:57 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id 36EC28FC23; Tue, 30 Nov 2010 02:10:56 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 99B7D509A5; Tue, 30 Nov 2010 01:52:33 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SoehBdLFhYQc; Tue, 30 Nov 2010 01:52:33 +0000 (GMT) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id 54587509A3 ; Tue, 30 Nov 2010 01:52:33 +0000 (GMT) Message-ID: <4CF458EE.7030109@langille.org> Date: Mon, 29 Nov 2010 20:52:46 -0500 From: Dan Langille Organization: The FreeBSD Diary User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: Terry Kennedy References: <01NUB1F8POL000BNN4@tmk.com> <01NUB3IOMZJW00BNN4@tmk.com> <01NUC6V4LBAQ00BNN4@tmk.com> In-Reply-To: <01NUC6V4LBAQ00BNN4@tmk.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ZFS panic after replacing log device X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2010 02:10:57 -0000 On 11/16/2010 8:41 PM, Terry Kennedy wrote: >> I would say it is definitely very odd that writes are a problem. Sounds >> like it might be a hardware problem. Is it possible to export the pool, >> remove the ZIL and re-import it? I myself would be pretty nervous trying >> that, but it would help isolate the problem? If you can risk it. > > I think it is unlikely to be a hardware problem. While I haven't run any > destructive testing on the ZFS pool, the fact that it can be read without > error, combined with ECC throughout the system and the panic always happen- > ing on the first write, makes me think that it is a software issue in ZFS. > > When I do: > > zpool export data; zpool remove data da0 > > I get a "No such pool: data". I then re-imported the pool and did: > > zpool offline data da0; zpool export data; zpool import data > > After doing that, I can write to the pool without a panic. But once I > online the log device and do any writes, I get the panic again. > > As I mentioned, I have this data replicated elsewere, so I can exper- > iment with the pool if it will help track down this issue. Any more news on this? -- Dan Langille - http://langille.org/