From owner-freebsd-fs@FreeBSD.ORG Sun Mar 24 19:19:55 2013 Return-Path: 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 483B661D for ; Sun, 24 Mar 2013 19:19:55 +0000 (UTC) (envelope-from chris@behanna.org) Received: from relay00.pair.com (relay00.pair.com [209.68.5.9]) by mx1.freebsd.org (Postfix) with SMTP id 06E4AFB6 for ; Sun, 24 Mar 2013 19:19:54 +0000 (UTC) Received: (qmail 28490 invoked by uid 0); 24 Mar 2013 19:19:54 -0000 Received: from 99.120.172.51 (HELO scythe.behanna.org) (99.120.172.51) by relay00.pair.com with SMTP; 24 Mar 2013 19:19:54 -0000 X-pair-Authenticated: 99.120.172.51 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: ZFS: Failed pool causes system to hang From: Chris BeHanna In-Reply-To: <514F4BD6.1060807@sneakertech.com> Date: Sun, 24 Mar 2013 14:19:53 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <3207E818-28B6-4F48-A100-4527F6D23936@behanna.org> References: <20130321044557.GA15977@icarus.home.lan> <514AA192.2090006@sneakertech.com> <20130321085304.GB16997@icarus.home.lan> <20130324153342.GA3687@icarus.home.lan> <20130324155448.GA4122@icarus.home.lan> <514F4BD6.1060807@sneakertech.com> To: FreeBSD FS X-Mailer: Apple Mail (2.1503) 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: Sun, 24 Mar 2013 19:19:55 -0000 On Mar 24, 2013, at 13:54 , Quartz wrote: >>> [...situations in which you *have* to reboot...] >=20 > [...all well and good, except for cases where someone has to = physically hit a button on a remote server...] >=20 >> People who run servers remotely yet lack this capability are >> intentionally choosing [snip] >=20 > Before you get up on a high horse and preach at me, consider a couple = things: >=20 > 1) Yes I can set that up, but this is a test box on my desk right now. >=20 > 2) A hard reset is a hard reset is a hard reset. I'm not bitching that = I have to physically walk over to the machine, I'm bitching that *THAT I = HAVE TO RESET IT*. Being able to reset it remotely is NOT an acceptable = solution or workaround, and has no bearing on my problem. Sure, there are bugs that inhibit the ability to reboot from = command-line. We shouldn't shrug them off, but we should also = acknowledge that the software is very complicated, and rooting out such = bugs takes time. Plus, this is a volunteer project. That said, there are some chassis that will let you drop to = lights-out management and force a reboot without having to physically = press a button, provided you have a way to reach the lights-out = management console. This often means, at least, a serial line = concentrator somewhere ("conserver" is simply awesome), or KVM-over-IP. Worst case, you have IP-addressable PDUs into which you can = telnet and hard-reset a particular outlet, to power-cycle a machine that = is truly, irrevocably stuck, without having to have a human walk over = and stick a paper clip into the reset hole. This should be a last = resort, though, as abrupt power-cycling shortens hardware life. --=20 Best, Chris BeHanna chris@behanna.org=