From owner-freebsd-fs@FreeBSD.ORG  Wed Apr 10 19:46:19 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 12D9D26E
 for <freebsd-fs@freebsd.org>; Wed, 10 Apr 2013 19:46:19 +0000 (UTC)
 (envelope-from quartz@sneakertech.com)
Received: from relay00.pair.com (relay00.pair.com [209.68.5.9])
 by mx1.freebsd.org (Postfix) with SMTP id ABC93643
 for <freebsd-fs@freebsd.org>; Wed, 10 Apr 2013 19:46:18 +0000 (UTC)
Received: (qmail 71529 invoked by uid 0); 10 Apr 2013 19:46:11 -0000
Received: from 173.48.104.62 (HELO ?10.2.2.1?) (173.48.104.62)
 by relay00.pair.com with SMTP; 10 Apr 2013 19:46:11 -0000
X-pair-Authenticated: 173.48.104.62
Message-ID: <5165C183.1020704@sneakertech.com>
Date: Wed, 10 Apr 2013 15:46:11 -0400
From: Quartz <quartz@sneakertech.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "Lawrence K. Chen, P.Eng." <lkchen@ksu.edu>
Subject: Re: ZFS: Failed pool causes system to hang
References: <499967956.5577199.1365621470123.JavaMail.root@k-state.edu>
In-Reply-To: <499967956.5577199.1365621470123.JavaMail.root@k-state.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: FreeBSD FS <freebsd-fs@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2013 19:46:19 -0000


> Other options are, failmode=continue is described that the system
> will continue on as if nothing has changed.

>Not
> sure what it means the system will continue

I'm not sure ether. In my experience, there's effectively no difference 
between "wait" and "continue".


> The other option is failmode=panic.  Which might be what you want in
> this case, since you can't shutdown gracefully with all I/O hanging.

Well, what I *WANT* is a way to kick the pool or something so that the 
rest of the machine still functions. As it stands, I can't even reliably 
get the status of the pool, as I can't reliably run half the zfs commands.

______________________________________
it has a certain smooth-brained appeal