From owner-freebsd-current Wed Apr 14 10: 8:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 78FA814F78 for ; Wed, 14 Apr 1999 10:08:22 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id SAA54285; Wed, 14 Apr 1999 18:06:00 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 14 Apr 1999 17:53:35 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 14 Apr 1999 17:53:34 +0000 To: current@freebsd.org From: Bob Bishop Subject: NFS, blocks of NULLs in files Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm getting the 'blocks of NULLs in NFS-mounted files' problem repeatably with last night's -current (cvsup'd at Wed Apr 14 04:02:34 BST 1999) running both on server and client (except that the client's kernel is 24hrs older than that). It happens during a kernel build on the client, so both the sources and objects are being accessed via NFS. During the 'generating linker set emulation glue for ELF' phase, a lot of the .o's turn up with blocks of NULLs. The rest of the world builds fine, but /usr/obj is local so there is little or no NFS writing going on in that case. The client is SMP but it's been doing daily builds with -j8 since that got sorted out, and anyway it now fails in exactly the same way whether -j is used or not. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message