Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Apr 1999 23:24:17 -0400 (EDT)
From:      Brian Feldman <green@unixhelp.org>
To:        Matthew Dillon <dillon@apollo.backplane.com>
Cc:        Alfred Perlstein <bright@rush.net>, current@FreeBSD.ORG
Subject:   Re: have live system with NFS client cache problems what do i do?
Message-ID:  <Pine.BSF.4.05.9904112323420.36814-100000@janus.syracuse.net>
In-Reply-To: <199904120231.TAA14835@apollo.backplane.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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 
> 					<dillon@backplane.com>
> 
> 
> 
> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9904112323420.36814-100000>