From owner-freebsd-fs@FreeBSD.ORG Sun May 6 17:50:08 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A565E106566B for ; Sun, 6 May 2012 17:50:08 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 5C8638FC0C for ; Sun, 6 May 2012 17:50:08 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id q46Ho7Fm011767; Sun, 6 May 2012 12:50:07 -0500 (CDT) Date: Sun, 6 May 2012 12:50:07 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Michael Richards In-Reply-To: Message-ID: References: <20120506123826.412881065672@hub.freebsd.org> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Sun, 06 May 2012 12:50:07 -0500 (CDT) Cc: "freebsd-fs@freebsd.org" Subject: Re: ZFS Kernel Panics with 32 and 64 bit versions of 8.3 and 9.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 May 2012 17:50:08 -0000 On Sun, 6 May 2012, Michael Richards wrote: > > I can accept the fact that some filesystem corruption may have > happened from the bad RAM. The issue now is recovering it. All the > hardware has been replaced but I cannot import the ZFS pool without > causing a kernel panic and that is the the problem here. To me it > matters not if the corruption occurred from RAM or the hard disk - I > don't think it's a good idea to blindly trust any filesystem data. At > minimum fail to import the pool but don't bring the entire system to a > halt. This isn't even a system drive - it's purely data. These are sentiments that I can agree with. If the import can be so dangerous, it seems that there should be a way to import the pool in a user-mode (outside if kernel space) so that issues can be fixed without panicing the kernel. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/