From owner-freebsd-stable@FreeBSD.ORG Sun Dec 30 12:05:11 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 B6CAD9C5 for ; Sun, 30 Dec 2012 12:05:11 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.18.15]) by mx1.freebsd.org (Postfix) with ESMTP id 6CDFE8FC13 for ; Sun, 30 Dec 2012 12:05:11 +0000 (UTC) Received: from [78.35.145.209] (helo=fabiankeil.de) by smtprelay03.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1TpHdX-0002WZ-3o; Sun, 30 Dec 2012 13:05:03 +0100 Date: Sun, 30 Dec 2012 12:32:13 +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: <20121230123213.2312fb47@fabiankeil.de> In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/RQ9advsrE4Yeh6r1.LexZy."; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 Cc: freebsd-stable@freebsd.org 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: Sun, 30 Dec 2012 12:05:11 -0000 --Sig_/RQ9advsrE4Yeh6r1.LexZy. Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Greg Bonett wrote: > Many months ago, I believe some *very bad hardware* caused corruption of a > file on one of my zfs file systems. I've isolated the corrupted file and > can reliably induce a kernel panic with "touch bad.file", "rm bad.file", = or > "ls -l" in the bad.file's directory (ls in bad.file's dir doesn't cause > panic, but "ls bad.file" does). >=20 > This is a raidz zpool, but zpool scrub doesn't fix it - it eventually > creates a kernel panic. >=20 > My next plan is to attempt to get rid of this file by zfs destroy(ing) the > entire filesystem. The corrupted file is on /tank, and I've copied all of > the good data onto a new zfs file system, /tank/tempfs/. 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. Fabian --Sig_/RQ9advsrE4Yeh6r1.LexZy. Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlDgJkEACgkQBYqIVf93VJ2Z1wCgnIo+kJ9OUxi3DTn7lgUqdnKH fXgAn1R2bsjOanhlAQZdAkORLdMgx6KS =Ej+3 -----END PGP SIGNATURE----- --Sig_/RQ9advsrE4Yeh6r1.LexZy.--