From owner-freebsd-stable@FreeBSD.ORG  Sat Dec 29 08:35:11 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 853CBF4A
 for <freebsd-stable@freebsd.org>; Sat, 29 Dec 2012 08:35:11 +0000 (UTC)
 (envelope-from greg.bonett@gmail.com)
Received: from mail-vb0-f50.google.com (mail-vb0-f50.google.com
 [209.85.212.50])
 by mx1.freebsd.org (Postfix) with ESMTP id 266EB8FC0C
 for <freebsd-stable@freebsd.org>; Sat, 29 Dec 2012 08:35:10 +0000 (UTC)
Received: by mail-vb0-f50.google.com with SMTP id fr13so11330986vbb.23
 for <freebsd-stable@freebsd.org>; Sat, 29 Dec 2012 00:35:10 -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=0kdEmmMvPk3gjTdk6pl/9wz7xv9X14qM/6GfHVtgtWo=;
 b=vrsqgHOnEVBe9/O+KHwDHWgNjpWb89D85GGkMr5g1HFpZxopSJPJyaxQE/KdJSaaSV
 Iku7pLKwXd4/8yVSzZbcTgEgeffdhGOiHcpfX9MNqI9uH5Bfml3YhKFX/lSoznhb1Nm0
 7fFdbkBb2XiuIFzgs/Ztk9uRaGXZ7+cpAVmZTtUC/FtqIP3Svqzc09Y61XIzjLjjgZ8u
 syGRqLBB6wdeosvTRmgcU03gnQ+UUxFGVtX2bV4MkHpjgwGHCCfKu58BxNc6B/a354x/
 K4KGAlcTStK/9EnAw5UY9oGCeZggxfIFwS9/bJlf2yBpehpP+AKvoavrncnoEOXdhqa9
 cXxg==
MIME-Version: 1.0
Received: by 10.220.115.19 with SMTP id g19mr54835557vcq.69.1356770110193;
 Sat, 29 Dec 2012 00:35:10 -0800 (PST)
Received: by 10.58.40.33 with HTTP; Sat, 29 Dec 2012 00:35:10 -0800 (PST)
In-Reply-To: <CACdU+f-K5bJ=fdO_kGARv95Hyeu-3mWKToi+0kbjFBRJRYQxjQ@mail.gmail.com>
References: <CAPceqYS4QTu=970XUE=KKV-ZdPSO6n5y1Dzuu4HM4yyie=-Gag@mail.gmail.com>
 <CACdU+f-K5bJ=fdO_kGARv95Hyeu-3mWKToi+0kbjFBRJRYQxjQ@mail.gmail.com>
Date: Sat, 29 Dec 2012 08:35:10 +0000
Message-ID: <CAPceqYTv+bzb5KvSZUZwGk6jbe-6xYzvXunxrZOodF-X25ML2w@mail.gmail.com>
Subject: Re: how to destroy zfs parent filesystem without destroying children
 - corrupted file causing kernel panick
From: Greg Bonett <greg.bonett@gmail.com>
To: Scot Hetzel <swhetzel@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: FreeBSD Stable <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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Dec 2012 08:35:11 -0000

>
> Does:
>
> cat /dev/null > bad.file
>
> Cause a kernel panic?
>
>
>
ah, sadly that does cause a kernel panic. I hadn't tried it though, thanks
for the suggestion.