Date: Sun, 24 Mar 2013 15:58:13 -0400 From: Quartz <quartz@sneakertech.com> To: Chris BeHanna <chris@behanna.org> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: ZFS: Failed pool causes system to hang Message-ID: <514F5AD5.8000006@sneakertech.com> In-Reply-To: <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> <3207E818-28B6-4F48-A100-4527F6D23936@behanna.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?514F5AD5.8000006>