Brian Reichert wrote:
/*
* 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
*
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
: 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
On Tue, Sep 25, 2001 at 09:54:34AM -0400, Matthew Emmerton wrote:
What OS is running on the NFS client and server?
My client is the 4.2-RELEASE box in question. There are several
servers, all of which (at this point) are Netapps.
--
Matthew Emmerton || [EMAIL PROTECTED]
GSI
[Should have included this in my earlier mail, sorry.]
In addition to bad cookies, I also see the following messages very
frequently:
NFS append race @0:954
They're issued in nfs/nfs_bio.c:
/*
* If dirtyend exceeds file size, chop it down. This should
Matthew Emmerton wrote:
What OS is running on the NFS client and server?
I see these too, with a FreeBSD-4.4 client and SunOS 5.5.1 servers. Seen them with
FreeBSD-4.2 clients to the same servers as well.
Lars
--
Lars Eggert [EMAIL PROTECTED] Information Sciences Institute
6 matches
Mail list logo
