From owner-freebsd-stable@FreeBSD.ORG  Sun Dec 30 07:30:55 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 6571661C;
 Sun, 30 Dec 2012 07:30:55 +0000 (UTC)
 (envelope-from greg.bonett@gmail.com)
Received: from mail-vb0-f47.google.com (mail-vb0-f47.google.com
 [209.85.212.47])
 by mx1.freebsd.org (Postfix) with ESMTP id 86DA98FC0A;
 Sun, 30 Dec 2012 07:30:54 +0000 (UTC)
Received: by mail-vb0-f47.google.com with SMTP id e21so12010357vbm.34
 for <multiple recipients>; Sat, 29 Dec 2012 23:30:48 -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=ZNMOlWPqNSvHkTevEs6iVn6+zbe7Rss7C8DEDKUlcA4=;
 b=SjqfqJlLe/8RjXgVZsSh8XJHXAnPvbd9o+d/0EoWTW2GqkeEIaFdDXrd3czfBmbY0X
 nDWfYiQCLJRqP/0fZwJtsLs1FvassRbO9sHHV4fOA2txSbHhRVsW0vIon3kPuhPgQF/3
 Hx8Zk7759phYkmfgC80dZvjFHqAg9d6rpppoGWArf0t8ESHetmDYTL+pT8ZmKGxDnBi6
 atZZKEo1/RTiINUrUHDgzsV6zVzhyHW//3DBkHgsFZ28oZ987KIo4kREQlbaY76vvfe3
 pqb8MYEG3SUorkfOG6nRQ8uMq+AsHtGssr1lqPBQ8ADV1zR3I02N9U6d1Ju46as6BKMY
 ECig==
MIME-Version: 1.0
Received: by 10.52.240.165 with SMTP id wb5mr51342367vdc.102.1356852648589;
 Sat, 29 Dec 2012 23:30:48 -0800 (PST)
Received: by 10.58.40.33 with HTTP; Sat, 29 Dec 2012 23:30:48 -0800 (PST)
In-Reply-To: <CAFqOu6gS-LYAK2rV+8_2A-FRrFQsahg==eMWEh3mp_QEJLyB0A@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>
 <CAFqOu6gS-LYAK2rV+8_2A-FRrFQsahg==eMWEh3mp_QEJLyB0A@mail.gmail.com>
Date: Sat, 29 Dec 2012 23:30:48 -0800
Message-ID: <CAPceqYQDHi-K12zpb8=ECh1x2mBMxPQk22+MJUpD++om61sctw@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: Artem Belevich <art@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
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 07:30:55 -0000

> 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.
>
> That's a good idea - but the zpool is made of geli devices.  Illumos can't
attached FreeBSD geli devices can it?