From owner-freebsd-stable Thu May 31 14:18:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from jaguar.ir.miami.edu (jaguar.ir.miami.edu [129.171.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 27EAD37B43E for ; Thu, 31 May 2001 14:18:44 -0700 (PDT) (envelope-from marcus@miami.edu) Received: from jaguar.ir.miami.edu (jaguar.ir.miami.edu [129.171.32.10]) by jaguar.ir.miami.edu (PMDF V6.0-24 #45575) with ESMTP id <0GE700HP5XV7P5@jaguar.ir.miami.edu> for freebsd-stable@freebsd.org; Thu, 31 May 2001 17:18:43 -0400 (EDT) Date: Thu, 31 May 2001 17:18:43 -0400 (EDT) From: Joe Clarke Subject: Re: bad cookie In-reply-to: <20010530113647.E91086@pcwin002.win.tue.nl> X-X-Sender: To: Stijn Hoop Cc: freebsd-stable@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII 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 I get this message from time to time on my FreeBSD NFS client. I have a very similar setup to yours. I found that this message is ignorable, though not something to cheer about. Someone pointed out that it could be a bad NIC or bad network device. I'm running with a fxp on the client and a dc on the server. My switches are Linksys el cheapos. I also don't use quite so many options in my mount. I find I get away with the default NFSv3 UDP just fine. I get decent performance on my ports builds. Joe Clarke On Wed, 30 May 2001, Stijn Hoop wrote: > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message