Date: Tue, 03 Jun 2008 07:55:14 +1000 From: Antony Mawer <fbsd-fs@mawer.org> To: Jeremy Chadwick <koitsu@FreeBSD.org> Cc: freebsd-fs@freebsd.org, Andrew Hill <lists@thefrog.net> Subject: Re: ZFS lockup in "zfs" state Message-ID: <48446C42.4070208@mawer.org> In-Reply-To: <20080602064023.GA95247@eos.sc1.parodius.com> References: <683A6ED2-0E54-42D7-8212-898221C05150@thefrog.net> <20080518124217.GA16222@eos.sc1.parodius.com> <93F07874-8D5F-44AE-945F-803FFC3B9279@thefrog.net> <16a6ef710806012304m48b63161oee1bc6d11e54436a@mail.gmail.com> <20080602064023.GA95247@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeremy Chadwick wrote: > On Mon, Jun 02, 2008 at 04:04:12PM +1000, Andrew Hill wrote: ... >> unfortunately i couldn't get a backtrace or core dump for 'political' >> reasons (the system was required for use by others) but i'll see if i can >> get a panic happening after-hours to get some more info... > > I can't tell you what to do or how to do your job, but honestly you > should be pulling this system out of production and replacing it with a > different one, or a different implementation, or a different OS. Your > users/employees are probably getting ticked off at the crashes, and it > probably irritates you too. The added benefit is that you could get > Scott access to the box. It's a home fileserver rather than a production "work" system, so the challenge is finding another system with an equivalent amount of storage.. :-) As one knows these things are often hard enough to procure out of a company budget, let alone out of ones own pocket! --Antony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48446C42.4070208>