From owner-freebsd-stable@FreeBSD.ORG Wed Apr 4 13:59:12 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 024EE16A402 for ; Wed, 4 Apr 2007 13:59:12 +0000 (UTC) (envelope-from chris#@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.freebsd.org (Postfix) with ESMTP id CE33813C487 for ; Wed, 4 Apr 2007 13:59:10 +0000 (UTC) (envelope-from chris#@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id l34Dwut2044695 for ; Wed, 4 Apr 2007 06:59:06 -0700 (PDT) (envelope-from chris#@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id l34DwucN044694 for freebsd-stable@freebsd.org; Wed, 4 Apr 2007 06:58:56 -0700 (PDT) (envelope-from chris#@1command.com) X-Authentication-Warning: mail.1command.com: www set sender to chris#@1command.com using -f Received: from brickwall.spam-fighters.com (brickwall.spam-fighters.com [216.177.243.55]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Wed, 04 Apr 2007 06:58:56 -0700 Message-ID: <20070404065856.m5gtplingo0kwgkw@webmail.1command.com> X-Priority: 3 (Normal) Date: Wed, 04 Apr 2007 06:58:56 -0700 From: "Chris H." To: freebsd-stable@freebsd.org References: <200704041309.l34D9da90685@lakes.dignus.com> In-Reply-To: <200704041309.l34D9da90685@lakes.dignus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) 4.1 Professional (not for redistribution) / FreeBSD-5.5 Subject: Re: NFS == lock && reboot 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: Wed, 04 Apr 2007 13:59:12 -0000 Quoting Thomas David Rivers : > Hi Chris, > > Well - the NFS server is 4.5-RELEASE - a rather old box. > > Everything worked fine when the shop was all 4.x boxes, but as soon > as we put in a 5.x or 6.x box - the NFS clients on those (5.x/6.x) boxes > locked up hard if rpc.lockd was running on the 4.5-RELEASE server. > > On 4.x, rpc.lockd doesn't start automatically - since, as I understand > it, rpc.lockd had "issues" in that timeframe. But, one of the developers > here turned it on hoping to get real locking for /var/mail. > > So - I thought my problem might simply be the old rpc.lockd > implementation in 4.x, and I didn't worry about it (since 4.x is > out-of-service anyway.) > > However, this sounded _so_ familiar - I thought I would pop-up > and mumble something like a "me too." > > rpc.statd isn't running on the 4.5 NFS server. > > > - Dave Rivers - Hello Dave, and thanks for responding. Alrighty then. Looks like it's time for a little more experimentation. I'm going to turn off both rpc.lockd and rpc.statd on this (and the others) and see if the NFS service(s) work a little more as intended. If it does, that'll be great. But doesn't cure an /apparently/ ailing NFS. I'll report back on my findings here. FWIW for anyone that might be interested; I am willing to make this boxen a guinie pig/lab rat in an effort to discover what might be wrong in the NFS family of services in FBSD. If interested, let me know what needs to be done. Thanks again for responding. --Chris > > >> >> Quoting Thomas David Rivers : >> >> > I have found that if I kill rpc.lockd on the NFS server, >> > most of the NFS issues I have (including a similar lock-up on >> > 6.1-RELEASE) go away. >> >> Ah hah! I wondered about this. Funny you mention it. The interesting >> thing was that my most problem boxen is this one here, and it is the >> /only/ one with: >> >> rpc_lockd_enable="YES" >> rpc_statd_enable="YES" >> >> in rc.conf I simply chose these in an effort to keep everything current >> and accurate. You don't happen to have any experiences keeping rpc.statd >> running? >> >> Thank you for taking the time to reply. >> >> --Chris > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- panic: kernel trap (ignored) ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 /////////////////////////////////////////////////////////////////