From owner-freebsd-fs@FreeBSD.ORG Tue Apr 9 10:47:40 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1CD10927 for ; Tue, 9 Apr 2013 10:47:40 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.freebsd.org (Postfix) with SMTP id B4DD3D0 for ; Tue, 9 Apr 2013 10:47:39 +0000 (UTC) Received: (qmail 90764 invoked by uid 0); 9 Apr 2013 10:40:58 -0000 Received: from 173.48.104.62 (HELO ?10.2.2.1?) (173.48.104.62) by relay03.pair.com with SMTP; 9 Apr 2013 10:40:58 -0000 X-pair-Authenticated: 173.48.104.62 Message-ID: <5163F03B.9060700@sneakertech.com> Date: Tue, 09 Apr 2013 06:40:59 -0400 From: Quartz 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." Subject: Re: ZFS: Failed pool causes system to hang References: <2092374421.4491514.1365459764269.JavaMail.root@k-state.edu> In-Reply-To: <2092374421.4491514.1365459764269.JavaMail.root@k-state.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2013 10:47:40 -0000 > So, you're not really waiting a long time.... I still don't think you're 100% clear on what's happening in my case. I'm trying to explain that my problem is *prior* to the motherboard resetting, NOT after. If I hard-reset the machine with the front panel switch, it boots just fine every time. When my pool *FAILS* (ie; is unrecoverable because I lost too many drives) it hangs effectively all io on the entire machine. I can't cd or ls directories, I can't run any zfs commands, and I can't issue a reboot or halt. This is a hang. The machine is completely useless in this state. There is no disk or cpu activity churning. There's no pool (anymore) to be trying to resilver or whatever anyway. I'm not going to wait 3+ hours for "shutdown -r now" to bring the machine down. Especially not when I already know that zfs won't let it. ______________________________________ it has a certain smooth-brained appeal