From owner-freebsd-stable Mon Feb 11 22:16:59 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 1A93137B402 for ; Mon, 11 Feb 2002 22:16:56 -0800 (PST) Received: from 12-234-22-238.client.attbi.com ([12.234.22.238]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020212061119.MBTW1147.rwcrmhc52.attbi.com@12-234-22-238.client.attbi.com>; Tue, 12 Feb 2002 06:11:19 +0000 Received: from master.gorean.org (root@master.gorean.org [10.0.0.2]) by 12-234-22-238.client.attbi.com (8.11.6/8.11.6) with ESMTP id g1C6BIq25368; Mon, 11 Feb 2002 22:11:18 -0800 (PST) (envelope-from DougB@FreeBSD.org) Received: from localhost (doug@localhost) by master.gorean.org (8.11.6/8.11.6) with ESMTP id g1C6BIW19409; Mon, 11 Feb 2002 22:11:18 -0800 (PST) (envelope-from DougB@FreeBSD.org) Date: Mon, 11 Feb 2002 22:11:17 -0800 (PST) From: Doug Barton X-X-Sender: doug@master.gorean.org To: Frank Volf Cc: freebsd-stable@FreeBSD.org Subject: Re: NFS error messages on 4.5-STABLE In-Reply-To: <20020210165232.99F413E08@drawbridge.oasis.IAEhv.nl> Message-ID: <20020211220951.T18729-100000@master.gorean.org> 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 On Sun, 10 Feb 2002, Frank Volf wrote: > > I (iregularly) get this kind of messages that belong to the NFS sub system. > > Feb 9 02:57:36 avalon /kernel: NFS append race @0:514 > Feb 9 02:57:36 avalon /kernel: NFS append race @0:274 > Feb 9 02:57:37 avalon /kernel: NFS append race @0:513 > Feb 9 16:31:09 avalon /kernel: got bad cookie vp 0xc4d23b80 bp 0xc17af54c > > Avalon is an NFS client, the NFS server has not logged any NFS related > messages in the same time frame. You already got the answer that these aren't serious unless you're getting a lot of them, or they correspond with access problems. However, by default our syslog.conf leaves off some levels or categories of syslog stuff, so you might want to put something like: *.* /var/log/all in your conf file, touch the file, then hup syslogd just to be sure. Good luck, Doug -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message