Date: Sat, 13 Apr 2013 09:39:10 +0100 From: "N.J. Mann" <njm@njm.me.uk> To: Quartz <quartz@sneakertech.com> Cc: freebsd-fs@freebsd.org Subject: Re: A failed drive causes system to hang Message-ID: <20130413083910.GA73903@titania.njm.me.uk> In-Reply-To: <516912E0.8080708@sneakertech.com> References: <mailman.11.1365681601.78138.freebsd-fs@freebsd.org> <51672164.1090908@o2.pl> <41A207817BC94167B0C94133EC0DFD68@multiplay.co.uk> <51687881.4080005@o2.pl> <20130412212207.GA81897@icarus.home.lan> <5168864A.2090602@sneakertech.com> <20130412222005.GA82884@icarus.home.lan> <516912E0.8080708@sneakertech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <516912E0.8080708@sneakertech.com>,
Quartz (quartz@sneakertech.com) wrote:
>
> > My point is that the PC-BSD folks need to be made aware of this issue,
> > so their iXSystems folks can help out if necessary and so on. If
> > they're left out of the loop, then that's bad for everyone.
>
> I was under the impression that pcbsd was entirely an "apps and UI"
> thing, and that low level stuff like cam or zfs wouldn't be their area
> of expertise, or even really their responsibility since they're not
> messing with any of that.
They have made changes to the way the system boots, e.g. files in
/etc/rc.d have be changed and some of the loader's Forth files. While
this may have no impact in this particular case it may be relevant in
other cases where users of PC-BSD are experiencing problems.
Cheers,
Nick,
--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130413083910.GA73903>