Date: Fri, 15 Jan 1999 16:10:07 +0100 From: "D. Rock" <rock@cs.uni-sb.de> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Satoshi Asami <asami@FreeBSD.ORG>, skynyrd@opus.cts.cwu.edu, freebsd-current@FreeBSD.ORG Subject: Re: NFS woes: getting worse? Message-ID: <369F5A4F.4918539B@cs.uni-sb.de> References: <199901150821.AAA35744@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have similar experiences. I sometimes do a "make release" with an NFS mounted chroot environment. My latest successful build is dated from Dec 21. All of the later builds (starting Jan 6th) failed. The error seems to be very deterministic though. I have at least a lot of garbage in <chroot>/usr/include, with the usual 0-Bytes starting on page boundary (but never the first page) up to the end of the file. I looked at the cvs log, but the only NFS/vfs/vm change I discovered (I'm using only NFSv2/UDP, so the one for NFSv3 on Solaris 7 doesn't apply) were the removal of "waslocked" paramter on Jan 5th. I don't know if this is related, though. Daniel Matthew Dillon schrieb: > > :Forgot to mention, this happens with a read-only NFS tree too. I was > :running builds on the client with a shared /usr/ports and WRKDIRPREFIX > :pointing to a local directory, and the build will topple over in the > :middle unable to find a Makefile on the server or something. > : > :That is the problem that went away with the server load. > : > :Satoshi > > I am running a Dec 24th CVS tree while working on the first set of VM > commits. > > I've been using read-only NFS mounts of /usr/src on diskless workstations > in order to do make -j6 buildworld runs on them ( /usr/obj being a big > 300 MB MFS filesystem on the same workstation, swap-backed, where swap > itself is BOOTP NFS based swap). > > I have not experienced any NFS corruption at all, so whatever blew NFS up > must have been committed after Dec 24th. Note that I *AM* using luoqi's > VFS/BIO patches, which fixed the msdosfs mount-after-ufs-mount-attempt > crash. > > I'll have time to help track down the NFS problems after the tree splits > and I can commit the new swapper, but I can't update my tree until then. > > -Matt > 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?369F5A4F.4918539B>