From owner-freebsd-current  Mon Apr 12 11:59:55 1999
Delivered-To: freebsd-current@freebsd.org
Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2])
	by hub.freebsd.org (Postfix) with ESMTP id E903715B10
	for <current@FreeBSD.ORG>; Mon, 12 Apr 1999 11:59:45 -0700 (PDT)
	(envelope-from sobomax@altavista.net)
Received: from altavista.net (async3-46.iptelecom.net.ua [212.42.68.237])
	by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id VAA14135;
	Mon, 12 Apr 1999 21:57:40 +0300 (EEST)
	(envelope-from sobomax@altavista.net)
Message-ID: <37124221.B8D7C471@altavista.net>
Date: Mon, 12 Apr 1999 21:57:37 +0300
From: Maxim Sobolev <sobomax@altavista.net>
X-Mailer: Mozilla 4.51 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Alfred Perlstein <bright@rush.net>
Cc: current@FreeBSD.ORG
Subject: Re: have live system with NFS client cache problems what do i do?
References: <Pine.BSF.3.96.990411195901.4169K-100000@cygnus.rush.net>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hey I have pretty the same problems on my 4.0 cvsup'ed and builded few
days ago!

As NFS server I have 3.1-stable box. 

Sincerely,

Maxim Sobolev

Alfred Perlstein wrote:

> Hey, i was just doing a kernel compile over NFS and i have a weird
> situtation.  After compiling everything the linker barfs on linking.
>
> gensetdefs: cd9660_bmap.o: not an ELF file
>
> for about 12 files...
>
> the compile is being done on a laptop that has my desktop's src dir
> NFS mounted.
>
> the card in the laptop is a 3comIII and the dekstop a pn0
>
> doing a 'file cd9660_bmap.o' on laptop (NFS client) gives me a
> cd9660_bmap.o: MS Windows COFF Unknown CPU
>
> while on the server:
> strlen.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), not stri
>
> it seems my client is having a really tough time with these files, i have
> copied the files that the client has corrupted to localdisk but now
> they seem fine...
>
> the client laptop is unable to link the kernel it's getting tons of
> corrupted data is seems, on the server i am able to link the kernel just
> fine.
>
> i'm using the default NFS mounts and no nfsiod.
>
> enabling nfsiod didn't help, however unmounting the NFS share and
> remounting seems to have fixed it....
>
> i guess i should have taken a crash dump when the system was all
> hosed but it's fine now... *sigh*
>
> Alfred Perlstein - Admin, coder, and admirer of all things BSD.
> -- There are operating systems, and then there's FreeBSD.
> -- http://www.freebsd.org/                        4.0-current
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message


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