From owner-freebsd-fs@FreeBSD.ORG Sun Mar 24 19:58:21 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 3156D1000 for ; Sun, 24 Mar 2013 19:58:21 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.freebsd.org (Postfix) with SMTP id CA9A51C7 for ; Sun, 24 Mar 2013 19:58:20 +0000 (UTC) Received: (qmail 78655 invoked by uid 0); 24 Mar 2013 19:58:13 -0000 Received: from 173.48.104.62 (HELO ?10.2.2.1?) (173.48.104.62) by relay02.pair.com with SMTP; 24 Mar 2013 19:58:13 -0000 X-pair-Authenticated: 173.48.104.62 Message-ID: <514F5AD5.8000006@sneakertech.com> Date: Sun, 24 Mar 2013 15:58:13 -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: Chris BeHanna Subject: Re: ZFS: Failed pool causes system to hang 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> <3207E818-28B6-4F48-A100-4527F6D23936@behanna.org> In-Reply-To: <3207E818-28B6-4F48-A100-4527F6D23936@behanna.org> Content-Type: text/plain; charset=ISO-8859-1; 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: Sun, 24 Mar 2013 19:58:21 -0000 > 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. No, I'm not trying to say that I expect something as complicated as a whole OS to be bug free, and I do well recognize that it's no one's obligation to fix anything anyway.... I'm just saying that starting an argument about the remote-ness of the reboot is missing the point. > Worst case, you have IP-addressable PDUs That's what we usually go with- guaranteed to work with any hardware. That plus a vnc capable kvm. ______________________________________ it has a certain smooth-brained appeal