From owner-freebsd-stable@FreeBSD.ORG Tue Oct 16 20:32:56 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3C1516A417 for ; Tue, 16 Oct 2007 20:32:56 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id DA69D13C4AA; Tue, 16 Oct 2007 20:32:55 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47151FF7.2080501@FreeBSD.org> Date: Tue, 16 Oct 2007 22:32:55 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "Chris H." , freebsd-stable@freebsd.org References: <20071004165755.GA1049@pp.htv.fi> <47120D83.1010703@FreeBSD.org> <20071015203202.GA17964@pp.htv.fi> <20071016004637.GA79351@cdnetworks.co.kr> <20071016185714.GB2186@pp.htv.fi> <20071016130146.pfyan4vs5cwgsoc0@webmail.1command.com> <20071016202251.GC4047@lava.net> In-Reply-To: <20071016202251.GC4047@lava.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Reproducable, possibly NFS related, fatal double fault in 6.2-R-p7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2007 20:32:56 -0000 Clifton Royston wrote: > On Tue, Oct 16, 2007 at 01:01:46PM -0700, Chris H. wrote: >> excerpt from this list titled: NFS == lock && reboot, that I posted follows: >> >> ------8<---SNIP---8<-----SNIP-----8<------- >> # uname -a >> FreeBSD host.domain.tld 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 26 >> 16:27:14 PST 2007 >> >> Greetings, >> Does anyone know when NFS and friends will be working again? I haven't >> been able >> to /safely/ use it from 4.8 on. I remember some talk on the list >> sometime ago and >> then it seemed to be resolved, as the discussion ended. So I thought it was >> fixed. Seems not. :( >> >> My scenario; >> mount host off root: >> mount script exec'd follows... >> >> #!/bin/sh - >> mount -t nfs host.domain.tld:/ /host >> mount -t nfs host.domain.tld:/var /host/var >> >> confirm mount... >> >> # ls /host >> .snap COPYRIGHT bin >> ... >> usr var tmp >> >> OK looks good... >> >> # cp /path/to/approx/10Mb/file /host/path/to/dest/dir/ >> >> Fatal double fault >> eis 0x0blah >> eiblah blah0x >> panic double fault >> no dump device defined >> rebooting in 15sec... >> >> Hmmm... that's not good. :( >> >> ------8<---SNIP---8<-----SNIP-----8<------- >> >> My final solution was to change the lines in /etc/rc.conf >> from: >> nfs_client_enable="YES" >> nfs_reserved_port_only="YES" >> nfs_server_enable="YES" >> rpc_lockd_enable="YES" >> rpc_statd_enable="YES" >> rpcbind_enable="YES" >> >> to: >> nfs_client_enable="YES" >> nfs_reserved_port_only="YES" >> nfs_server_enable="YES" >> #rpc_lockd_enable="YES" >> #rpc_statd_enable="YES" >> rpcbind_enable="YES" >> >> Making those changes ended the "Fatal double fault && reboot in 15 >> seconds..." > > Thanks for this very timely mention! The cluster of servers I am > about to upgrade from 4.8 to 6.2 relies heavily on > NFS to an old Netapp. If I have got to disable rpc_lockd and > rpc_statd, it's good to know that now! > > Can I ask, can anybody confirm that they're running 6.2 on NFS > successfully *with* lockd and statd? Er, yes, of course it does. The old message he is quoting is bogus on its own, I don't know if he ever was able to provide meaningful traces but it may well be nve as in the upthread discussion. Kris