From owner-freebsd-stable Wed May 30 2:37:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by hub.freebsd.org (Postfix) with ESMTP id 2DE1D37B423 for ; Wed, 30 May 2001 02:37:40 -0700 (PDT) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.11.3/8.11.3) id f4U9alk92357 for freebsd-stable@freebsd.org; Wed, 30 May 2001 11:36:47 +0200 (CEST) (envelope-from stijn) Date: Wed, 30 May 2001 11:36:47 +0200 From: Stijn Hoop To: freebsd-stable@freebsd.org Subject: bad cookie Message-ID: <20010530113647.E91086@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, What should I do with the following kernel error messages: got bad cookie vp 0xd19d6bc0 bp 0xc61d72bc got bad cookie vp 0xd1480180 bp 0xc616fbec After grepping the source, I discovered that this was an NFS problem (it's not really obvious from the message, is it?). I have two machines involved, no more, with server: FreeBSD 4.3-RELEASE #0: Mon Apr 23 13:04:32 CEST 2001 handstarted with # /usr/sbin/portmap # /sbin/mountd -r # /sbin/nfsd -u -t -n 4 client: FreeBSD 4.3-STABLE #0: Wed May 16 04:41:06 CEST 2001 handstarted with # /sbin/nfsiod -n 4 # sysctl -w vfs.nfs.access_cache_timeout=2 (both sequences taken from /etc/rc.network - no /etc/rc.d/nfs.sh start unfortunately :( ) I then mounted with: mount -t nfs -o nfsv3,tcp,intr,rdirplus,-r=32768,-w=32768 server:/path /mnt Both machines have a 3com 905 ethernetcard (xl0), are on the same 100mbit switch, and are running 100baseTX full duplex. The client is a faster machine then the server however (P3-933 vs. P2-400). Both machines are otherwise very lightly loaded. Should I loose some options? Should I disregard the message? I think I get this message because I'm running an application that accesses a lot of files in the same directory. Unfortunately, around the time when this message occurs, the application also stops running, with the job half done :( --Stijn -- SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message