From owner-freebsd-questions Sun Jun 24 7:49: 2 2001 Delivered-To: freebsd-questions@freebsd.org Received: from smithers.stomped.com (smithers.stomped.com [216.17.56.2]) by hub.freebsd.org (Postfix) with SMTP id B229D37B406 for ; Sun, 24 Jun 2001 07:48:58 -0700 (PDT) (envelope-from malhavoc@stomped.com) Received: (qmail 67679 invoked by uid 1041); 24 Jun 2001 14:49:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 24 Jun 2001 14:49:06 -0000 Date: Sun, 24 Jun 2001 09:49:06 -0500 (CDT) From: Jason Nugent To: Subject: NFS not working after kernel rebuild Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greetings, Just a question regarding NFS in 4.3-RELEASE. I've got a machine that had been running a version of 4.3-STABLE (I had been using cvsup to get the latest source) that was a few months old. The box had been serving as a NFS client and had been working flawlessly. Just recently (two days ago), I did another poll of cvsup to grab the latest STABLE version of the FreeBSD 4 tree. My new kernel had essentially the same config as the previous one, and contains these lines: options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required and also contained the conf options in rc.conf to start nfsiod: nfs_client_enable="YES" nfs_client_flags="-n 4" When I reboot my machine with this kernel, however, all the necessary processes start correctly (nfsiod, portmap, et al), but I get this in /var/log/messages: Jun 24 09:14:24 web1 /kernel: Starting final network daemons: Jun 24 09:14:25 web1 /kernel: nfsiod Jun 24 09:14:25 web1 /kernel: NFS access cache time=4 Jun 24 09:14:25 web1 /kernel: rpc.umntall: Jun 24 09:14:25 web1 /kernel: gethostbyname(titan) failed Jun 24 09:14:25 web1 /kernel: the last three lines are repeated for each nfs file partition I'm attempting to mount. I had first thought that my firewall rules weren't working, so I turned off firewall_enable and set default to accept and rebooted, but the same error was occuring. Does anyone have a comment or an idea? This isn't critical since I have a working kernel based on a previous version of 4.3-STABLE, but it'd be nice to have the latest once again. Thanks in advance, Jason ---------------------- Jason Nugent Aka MalHavoc Server Programmer and Administrator S T O M P E D . C O M For PGP public key: http://malhavoc.stomped.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message