From owner-freebsd-fs@FreeBSD.ORG Mon Jun 2 22:26:17 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4ED2A1065679; Mon, 2 Jun 2008 22:26:17 +0000 (UTC) (envelope-from fbsd-fs@mawer.org) Received: from outbound.icp-qv1-irony-out4.iinet.net.au (outbound.icp-qv1-irony-out4.iinet.net.au [203.59.1.150]) by mx1.freebsd.org (Postfix) with ESMTP id A00138FC12; Mon, 2 Jun 2008 22:26:16 +0000 (UTC) (envelope-from fbsd-fs@mawer.org) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ah8BANcIREjLzq3r/2dsb2JhbAAIrw8 X-IronPort-AV: E=Sophos;i="4.27,579,1204470000"; d="scan'208";a="229934898" Received: from unknown (HELO [10.24.1.1]) ([203.206.173.235]) by outbound.icp-qv1-irony-out4.iinet.net.au with ESMTP; 03 Jun 2008 05:57:06 +0800 Message-ID: <48446C42.4070208@mawer.org> Date: Tue, 03 Jun 2008 07:55:14 +1000 From: Antony Mawer User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Jeremy Chadwick 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> In-Reply-To: <20080602064023.GA95247@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Andrew Hill Subject: Re: ZFS lockup in "zfs" state X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2008 22:26:17 -0000 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