From owner-freebsd-hackers Tue Sep 25 6:36:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id B2AF037B446 for ; Tue, 25 Sep 2001 06:36:44 -0700 (PDT) Received: (qmail 25519 invoked by uid 3001); 25 Sep 2001 13:36:43 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 25 Sep 2001 13:36:43 -0000 Received: (qmail 42475 invoked by uid 1001); 25 Sep 2001 13:36:43 -0000 Date: Tue, 25 Sep 2001 09:36:43 -0400 From: Brian Reichert To: freebsd-hackers@freebsd.org Subject: got bad cookie vp 0xe2e5ef80 bp 0xcf317328 Message-ID: <20010925093643.W49528@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm starting to see errors in /var/log/messages under 4.2-RELEASE: Sep 23 00:31:17 bmdb1 /kernel: got bad cookie vp 0xe2e5ef80 bp 0xcf317328 Not many, but more than one, and I've never seen this in my years of using FreeBSD. The code producing this message is in /usr/src/sys/nfs/nfs_bio.c, with this associated comment: /* * Yuck! The directory has been modified on the * server. The only way to get the block is by * reading from the beginning to get all the * offset cookies. * * Leave the last bp intact unless there is an error. * Loop back up to the while if the error is another * NFSERR_BAD_COOKIE (double yuch!). */ Is this an error that I need to worry about? Is this just my NFS client loosing track of some bookkeeping details? -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message