From owner-freebsd-current  Tue Apr 13  0:25:11 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 B99591527F
	for <current@FreeBSD.ORG>; Tue, 13 Apr 1999 00:25:02 -0700 (PDT)
	(envelope-from sobomax@altavista.net)
Received: from vega. (async3-31.iptelecom.net.ua [212.42.68.222])
	by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id KAA10929;
	Tue, 13 Apr 1999 10:22:53 +0300 (EEST)
	(envelope-from sobomax@altavista.net)
Received: from altavista.net (big_brother [192.168.1.1])
	by vega. (8.9.2/8.9.2) with ESMTP id KAA85849;
	Tue, 13 Apr 1999 10:21:33 +0300 (EEST)
	(envelope-from sobomax@altavista.net)
Message-ID: <3712F079.CDAD602@altavista.net>
Date: Tue, 13 Apr 1999 10:21:29 +0300
From: Maxim Sobolev <sobomax@altavista.net>
Reply-To: sobomax@altavista.net
Organization: Vega International Capital
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: ru,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.990412152025.4169R-100000@cygnus.rush.net>
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

 

Alfred Perlstein wrote:

> On Mon, 12 Apr 1999, Maxim Sobolev wrote:
>
> > 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.
> > >
> > 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.
>  

> Let's try to figure out some other commonalities to assist debugging this.
> can you please fill this in:
>  

                   Me                              You
Server version 4.0-apr6th                  3.1- apr6th
 Netcard       pn0                               ed0 (Realtek 8029)
 local disk    da                                  wd0
 options       softupdates                    noatime
 nfsd?         yes                                 yes
 ram           32meg                            24meg

Client version 4.0-apr9th                       4.0- apr6th
 Netcard       ep0 3comIII pcmcia       ed0 (AR-P500 pcmcia)
 local disk    wd                                   ad0
 options       softupdates                       noatime
 nfsiod        don't think so                    don't think so
 ram           48meg                                32meg

>  
> Mount type:    mount server:/usr/src
>                 /usr/src
>
> how bug        build kernel in
> happened:      NFS mounted /usr/src
>                make depend && make -j6 all
>
> bug:           client sees files are filled
>                with zeros, but server has
>                non-corrupted files
>
>                will not link on client
>                links fine on server
>                if the files are copied from
>                the NFS mount to local disk
>                they "un-corrupt" themselves.
>
> well?  I'm tempted to blame the 3com, but that doesn't make sense
> as when you copy to local disk the files seem to become normal again...
>  

Mount type:    mount -o noatime server:/usr/src
                      mount -o noatime server:/usr/ports

how bug        build ports and kernel
happened:      NFS mounted /usr/ports
                     cd /usr/ports/textproc/docproj
                     make all install
                     NFS mounted /usr/src
                     make depend && make -j4

bug:           client sees files are filled
                 with zeros, but server has
                 non-corrupted files

                 will not link on client
               links fine on server
               if the files are copied from
               the NFS mount to local disk
               they "un-corrupt" themselves.
               very good chance to link correctly is to try run make on client
once more (cache flushes??)




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