Date: Sun, 6 May 2012 12:50:07 -0500 (CDT) From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us> To: Michael Richards <hackish@gmail.com> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: ZFS Kernel Panics with 32 and 64 bit versions of 8.3 and 9.0 Message-ID: <alpine.GSO.2.01.1205061248070.1678@freddy.simplesystems.org> In-Reply-To: <CAPUouH2Ftt4ZDtanPmfTXa9%2BHRCkLCL=HcGqT9VgV%2BBrQcYE3A@mail.gmail.com> References: <20120506123826.412881065672@hub.freebsd.org> <alpine.GSO.2.01.1205060955450.1678@freddy.simplesystems.org> <CAPUouH2Ftt4ZDtanPmfTXa9%2BHRCkLCL=HcGqT9VgV%2BBrQcYE3A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.2.01.1205061248070.1678>