From owner-freebsd-current Sun Apr 11 20:26:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id DCD2815259 for ; Sun, 11 Apr 1999 20:26:35 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA36951; Sun, 11 Apr 1999 23:24:17 -0400 (EDT) Date: Sun, 11 Apr 1999 23:24:17 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon Cc: Alfred Perlstein , current@FreeBSD.ORG Subject: Re: have live system with NFS client cache problems what do i do? In-Reply-To: <199904120231.TAA14835@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 11 Apr 1999, Matthew Dillon wrote: > :/usr/obj isn't mounted, i'm just compiling a kernel. > : > :no i have no msdos mounted filesystems, i do however have an > :unmounted win98 partition and a cdrom with joliet extentions mounted > :however the cdrom only contains mp3s. > : > :After doing more data manipulation (copying files around to flush > :the NFS cache) it seems to reload the data then it finds them ok > :and tries to link, during the link i get missing references to > :several symbols, symbol sizes changed etc etc... > : > :Just seems like bad data. > : > :Now if i just go into the dir on the server and link the kernel > :it's fine, no problems whatsoever. (compile on local disk) > : > :-Alfred > : > :PS, i suspect the 3comIII card in the laptop # ep: 3Com 3C509 (buggy) > : > :NFS perfomance and stability in 3.1-stable and 4.0 have been surperb lately. > :one reboot when i was killing a low ram NFS server a few weeks ago and just > :this today (which could be the NIC) otherwise very impressive. > > Ok. This is something to watch, then. The corruption is worrysome. It > is odd to get this sort of corruption in a client's buffer cache when > all the file I/O is running over NFS. The real question is : where did > the corruption come from? The client's IDE drive or something originally > on the server? > > Are there any dos partitions on the server at all? If not, then the > corruption is occuring on the client. But if the make procedure is not > accessing (much of) the client's hard drive, where on the client could > the corruption be coming from? This has nothing to do with DOS. In case you didn't get my other hint: {"/home/green"}$ dd if=/dev/zero count=1 2>/dev/null | file - standard input: MS Windows COFF Unknown CPU > > -Matt > Matthew Dillon > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message