From owner-freebsd-stable@FreeBSD.ORG Mon Dec 31 14:32:39 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 505A569E for ; Mon, 31 Dec 2012 14:32:39 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de [80.67.31.97]) by mx1.freebsd.org (Postfix) with ESMTP id 0447C8FC08 for ; Mon, 31 Dec 2012 14:32:38 +0000 (UTC) Received: from [78.35.165.136] (helo=fabiankeil.de) by smtprelay05.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1TpgO0-0006ml-4l; Mon, 31 Dec 2012 15:30:40 +0100 Date: Mon, 31 Dec 2012 15:30:21 +0100 From: Fabian Keil To: Greg Bonett Subject: Re: how to destroy zfs parent filesystem without destroying children - corrupted file causing kernel panick Message-ID: <20121231153021.0fa0e98c@fabiankeil.de> In-Reply-To: References: <20121230123213.2312fb47@fabiankeil.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/oiRmnI4.8rjQxKtRe9TAlz="; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Dec 2012 14:32:39 -0000 --Sig_/oiRmnI4.8rjQxKtRe9TAlz= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Greg Bonett wrote: > > My next plan would be reporting the problem with sufficient > > information so the bug can be fixed. > > > > Destroying the dataset or the whole pool seems like papering over the > > real issue to me and you could still do it if the PR gets ignored for > > too long or a developer agrees that this is the only option. > > > > > ok, that's a good idea - do you know where I should report this problem? I'd start with freebsd-fs@ and file a proper PR if there's still no response after a few weeks or so. If you haven't already, you might want to skim through: http://www.freebsd.org/cgi/query-pr-summary.cgi?&text=3Dzfs first, to see if your problem is already known. > unfortunately, I don't know how I can provide the problematic file because > any read, cp, or mv causes kernel panic. Additional information about the panic itself will probably do at the beginning, you can always provide more later if someone asks for it. For details see: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html Fabian --Sig_/oiRmnI4.8rjQxKtRe9TAlz= Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlDhoZUACgkQBYqIVf93VJ05ewCguLlQSLKacrY4j2I5sLovm/5k RxYAn2CtmhcehYw6g29ncNLPGtiSVucz =gntc -----END PGP SIGNATURE----- --Sig_/oiRmnI4.8rjQxKtRe9TAlz=--