From owner-freebsd-stable  Fri Jun  1  0:12:50 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67])
	by hub.freebsd.org (Postfix) with ESMTP id B3FFA37B422
	for <freebsd-stable@FreeBSD.ORG>; Fri,  1 Jun 2001 00:12:48 -0700 (PDT)
	(envelope-from dillon@earth.backplane.com)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.3/8.11.2) id f517Ck780822;
	Fri, 1 Jun 2001 00:12:46 -0700 (PDT)
	(envelope-from dillon)
Date: Fri, 1 Jun 2001 00:12:46 -0700 (PDT)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200106010712.f517Ck780822@earth.backplane.com>
To: Joe Clarke <marcus@miami.edu>
Cc: Stijn Hoop <stijn@win.tue.nl>, freebsd-stable@FreeBSD.ORG
Subject: Re: bad cookie
References:  <Pine.OSF.4.31.0105311716210.31369-100000@jaguar.ir.miami.edu>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-stable>
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

    NFS clients use directory cookies to keep track of directory scans.
    If a directory changes out from under a client, then when it attempts
    to use a previously obtained cookie to continue a scan the NFS server
    may reply with a 'bad cookie' response.  The error is not fatal, it
    simply causes the client to rescan the directory from the beginning
    to locate the pickup point.

    A bad cookie can occur if several hosts modify (create, delete, rename
    files) in the same directory while (or near the time of) an NFS client
    doing a directory scan, or if the client-side cookie caches
    times out in the middle of a directory scan (which can happen under
    heavy loads). 

						-Matt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message