From owner-freebsd-current Sat Jan 30 05:20:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23891 for freebsd-current-outgoing; Sat, 30 Jan 1999 05:20:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23886 for ; Sat, 30 Jan 1999 05:20:47 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id FAA91643 for ; Sat, 30 Jan 1999 05:21:20 -0800 (PST) To: current@FreeBSD.ORG Subject: Even more interesting NFS problems.. Date: Sat, 30 Jan 1999 05:21:20 -0800 Message-ID: <91639.917702480@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scenario: Two machines, releng3.freebsd.org (running 3.0-stable) and current.freebsd.org (running 4.0-current). releng3 has all the disk space and is the NFS server. current is an NFS client and uses releng3 for its CVS repository, FTP snapshot stashing area, etc. As of the day before yesterday, I started getting all manner of NFS errors on "current" and checked the amd.conf file it was using. Version 3 of NFS seemed to be the default (!) for amd so I changed it to version 2 and rebooted both boxes. Still no change. When doing things like a cvs update from current using the cvs repo on releng3, I get this: root@usw2-> cvup U Makefile.inc1 U Makefile.upgrade ? make.out U bin/rm/rm.1 cvs update: cannot open /home/ncvs/src/contrib/groff/devps/HNI,v: RPC struct is bad That latter message is a new one in my experience. Anyone have any ideas? I might also add that this exact same setup worked great back when current.freebsd.org was running 3.0-current and releng3.freebsd.org was releng22.freebsd.org, running 2.2.8-stable. The only thing I changed were the OS versions and now we're also SNAPless. :-( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message