From owner-freebsd-current@FreeBSD.ORG Fri Dec 11 08:59:51 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 088531065670 for ; Fri, 11 Dec 2009 08:59:51 +0000 (UTC) (envelope-from jeremie@le-hen.org) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [212.27.42.1]) by mx1.freebsd.org (Postfix) with ESMTP id 67D3E8FC08 for ; Fri, 11 Dec 2009 08:59:48 +0000 (UTC) Received: from smtp1-g21.free.fr (localhost [127.0.0.1]) by smtp1-g21.free.fr (Postfix) with ESMTP id 141D194007C; Fri, 11 Dec 2009 09:59:43 +0100 (CET) Received: from endor.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp1-g21.free.fr (Postfix) with ESMTP id D9DFD940126; Fri, 11 Dec 2009 09:59:40 +0100 (CET) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id C595233E85; Fri, 11 Dec 2009 08:59:40 +0000 (UTC) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id AC504A127E; Fri, 11 Dec 2009 08:59:40 +0000 (UTC) Date: Fri, 11 Dec 2009 09:59:40 +0100 From: Jeremie Le Hen To: Andriy Gapon Message-ID: <20091211085940.GA7114@felucia.tataz.chchile.org> References: <20091210072147.GA4963@felucia.tataz.chchile.org> <4B20EAA3.5010009@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B20EAA3.5010009@icyb.net.ua> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-current@FreeBSD.org, Jeremie Le Hen Subject: Re: Panic while doing zfs rename 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: Fri, 11 Dec 2009 08:59:51 -0000 Hi Andriy, On Thu, Dec 10, 2009 at 02:33:39PM +0200, Andriy Gapon wrote: > on 10/12/2009 09:21 Jeremie Le Hen said the following: > ... > > % zfs_statfs(866b2a10,866b2a70,1d8,cb41c844,865a3a10,...) at zfs_statfs+0x39 > > % __vfs_statfs(866b2a10,cb41c844,0,0,0,...) at __vfs_statfs+0x1f > > % nullfs_statfs(865a3a10,865a3a70,806bd68b,865a3a70,865a3a10,...) at nullfs_statfs+0x46 > > % __vfs_statfs(865a3a10,865a3a70,1d8,a5889340,cb41cb78,...) at __vfs_statfs+0x1f > > And you also seem to have nullfs in the picture. > Did you by a chance renamed a zfs filesystem under nullfs? Unfortunately I can't tell you for sure. I'd say yes according to the backtrace... ISTR I did some tests to null-mount the _removed_ filesystem (former data/repos). I think the following rename from data/crepos to data/repos triggered something in the nullfs layer that led to this panic. Now I'm thinking about it, I remember doing a forced-destroy (-f) of the original data/repos. Would this mean the nullfs filesystem will panic if the underlying filesystem disappear? Unfortunately I can't afford crashing this server once more, to verify this. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >