From owner-freebsd-stable@FreeBSD.ORG  Sun Dec 30 06:59:48 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 6C56E260
 for <freebsd-stable@freebsd.org>; Sun, 30 Dec 2012 06:59:48 +0000 (UTC)
 (envelope-from artemb@gmail.com)
Received: from mail-la0-f47.google.com (mail-la0-f47.google.com
 [209.85.215.47])
 by mx1.freebsd.org (Postfix) with ESMTP id D1CDE8FC08
 for <freebsd-stable@freebsd.org>; Sun, 30 Dec 2012 06:59:47 +0000 (UTC)
Received: by mail-la0-f47.google.com with SMTP id fh20so2626581lab.20
 for <freebsd-stable@freebsd.org>; Sat, 29 Dec 2012 22:59:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
 bh=hqa9kOWvt1BOnO5ERXypbEe0Pt5X2R6nPr7W+poaGCc=;
 b=tVeahxzOcVO9bTxgDvl/gu8DqGi1I04QUQBYJPrQ+SiJigmWwlH7XRH4Yjj1mZt1am
 ZyC98pw6HkCNzLXfdznaA0EWbDB9ji4jwvV/OxA106L7yRYni8bR6HGskOeik+FCbqFD
 0CpCwtKNzNly1B/x9fm9BpYMCulGQL3QsXNrzRcdAmYuCSI+b+Vv2mWVol87rIgglwQg
 NE45GhnwnD0IDTFLrHXg1OkdThrvNnD8s9LBTkjfTFY+AVYTiwlkT+JQxUeRIs3+l3MP
 QS+vHZ1KJRsFGj34XGtQJtX1+71eqvLaIYQjXyGOc60WQMarst926bWYlNyLSFQejo33
 8m7w==
MIME-Version: 1.0
Received: by 10.152.110.18 with SMTP id hw18mr35976491lab.22.1356850786491;
 Sat, 29 Dec 2012 22:59:46 -0800 (PST)
Sender: artemb@gmail.com
Received: by 10.112.80.103 with HTTP; Sat, 29 Dec 2012 22:59:46 -0800 (PST)
In-Reply-To: <CAPceqYTv+bzb5KvSZUZwGk6jbe-6xYzvXunxrZOodF-X25ML2w@mail.gmail.com>
References: <CAPceqYS4QTu=970XUE=KKV-ZdPSO6n5y1Dzuu4HM4yyie=-Gag@mail.gmail.com>
 <CACdU+f-K5bJ=fdO_kGARv95Hyeu-3mWKToi+0kbjFBRJRYQxjQ@mail.gmail.com>
 <CAPceqYTv+bzb5KvSZUZwGk6jbe-6xYzvXunxrZOodF-X25ML2w@mail.gmail.com>
Date: Sat, 29 Dec 2012 22:59:46 -0800
X-Google-Sender-Auth: x5-ORv_LjGMnSF45Bt9BnWa09ys
Message-ID: <CAFqOu6gS-LYAK2rV+8_2A-FRrFQsahg==eMWEh3mp_QEJLyB0A@mail.gmail.com>
Subject: Re: how to destroy zfs parent filesystem without destroying children
 - corrupted file causing kernel panick
From: Artem Belevich <art@freebsd.org>
To: Greg Bonett <greg.bonett@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Scot Hetzel <swhetzel@gmail.com>,
 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: Sun, 30 Dec 2012 06:59:48 -0000

On Sat, Dec 29, 2012 at 12:35 AM, Greg Bonett <greg.bonett@gmail.com> wrote:
>
> >
> > 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.

It's probably a long shot, but you may try removing bad file using
illumos (ex opensolaris) system (or liveCD). In the past it used to be
a little bit more robust than FreeBSD when it came to dealing with
filesystem corruption. In one case I had illumos printed out a message
about corrupt pool and remained up and running while FreeBSD would
just crash when I tried mounting the pool.

--Artem