From owner-freebsd-current@FreeBSD.ORG Sun Feb 10 23:43:51 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C55B16A41A for ; Sun, 10 Feb 2008 23:43:51 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 25A8113C457 for ; Sun, 10 Feb 2008 23:43:51 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 3064C2084; Mon, 11 Feb 2008 00:43:42 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 1E7D52082; Mon, 11 Feb 2008 00:43:41 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 815D984492; Mon, 11 Feb 2008 00:43:41 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Vladimir Botka References: <3E1A8014-3F18-492B-8288-46706F420123@altesco.nl> <9892EE5A-068E-4BFA-8D31-9FF7184C3181@altesco.nl> <20080209093146.732f5e03@srv> Date: Mon, 11 Feb 2008 00:43:41 +0100 In-Reply-To: <20080209093146.732f5e03@srv> (Vladimir Botka's message of "Sat\, 9 Feb 2008 09\:31\:46 +0100") Message-ID: <86ejbk2x8y.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: Panic when connecting USB drive to amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Feb 2008 23:43:51 -0000 Vladimir Botka writes: > error message says: > Fatal trap 12: page fault while in kernel mode > fault code =3D supervisor read data, page not present > > My guess is that the process cannot access memory (because there is > none left). As I know ZFS is greedy, so unless you have 16 processor Sun > Enterprise with 64GB memory you should better to switch back to UFS. Your "guess" is incorrect, and I get the impression that you wrote this just out of spite. Yes, ZFS can run an improperly tuned system out of memory, but the panic message in that situation is completely different from the one reported here. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no