From owner-freebsd-stable@FreeBSD.ORG Sat Dec 29 07:47:05 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 3F96EAC9 for ; Sat, 29 Dec 2012 07:47:05 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from mail-ia0-f174.google.com (mail-ia0-f174.google.com [209.85.210.174]) by mx1.freebsd.org (Postfix) with ESMTP id F22478FC08 for ; Sat, 29 Dec 2012 07:47:04 +0000 (UTC) Received: by mail-ia0-f174.google.com with SMTP id y25so9185262iay.5 for ; Fri, 28 Dec 2012 23:46:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Y7Va5j9s6VVrth/jvEd9h+mllXoMXEesgHx8aXiugBE=; b=r6wvVOza026Qc39oKSAOklpj56WI7NCgNgL2r0AH3TSCwuoSGieAZ90rWm9Fr0LIk0 sj5l405Kf/mfG7ZhX/jxAhOF2bk1ijJuXunabxyAO+p8LUbFeROjY/Kbp6xNOivp6se1 E1RLnaOxORrcuL+jfStbzXjIJ05aXxWvB38zyCeH9w/AL2Mm4QtSkNLVNZEVfWsGdwvV bEpIYs+tMgD4CZ/Hpufjat0T0+1OEtCpobBe6SKgoMT1FQ9Tz2UgCRM4SNFsY0jCXeHL upU3fqD007BTJtajgCUWOuEln0D7DNq6D+Wwemm5GLce7C9XgP6d9fCqeTlcidTULOZC 4fdg== MIME-Version: 1.0 Received: by 10.50.91.168 with SMTP id cf8mr32015247igb.20.1356767218344; Fri, 28 Dec 2012 23:46:58 -0800 (PST) Received: by 10.50.192.167 with HTTP; Fri, 28 Dec 2012 23:46:58 -0800 (PST) In-Reply-To: References: Date: Sat, 29 Dec 2012 01:46:58 -0600 Message-ID: Subject: Re: how to destroy zfs parent filesystem without destroying children - corrupted file causing kernel panick From: Scot Hetzel To: Greg Bonett Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 29 Dec 2012 07:47:05 -0000 On Fri, Dec 28, 2012 at 2:46 PM, 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). > Does: cat /dev/null > bad.file Cause a kernel panic? -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised.