From owner-freebsd-current Tue Oct 13 08:15:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03576 for freebsd-current-outgoing; Tue, 13 Oct 1998 08:15:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03564 for ; Tue, 13 Oct 1998 08:14:55 -0700 (PDT) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id RAA24626 for ; Tue, 13 Oct 1998 17:14:30 +0200 (CEST) Received: from cs.uni-sb.de (acc2-156.telip.uni-sb.de [134.96.112.156]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id RAA26455 for ; Tue, 13 Oct 1998 17:14:29 +0200 (CEST) Message-ID: <36236E98.43A3CDC6@cs.uni-sb.de> Date: Tue, 13 Oct 1998 17:15:36 +0200 From: Daniel Rock X-Mailer: Mozilla 4.06 [de] (Win98; U) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: -current NFS problem References: <199810130405.VAA18347@math.berkeley.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have also seen NFS problems for some months now: (NFS Server is a Solaris 2.6 box) - During a "make release" with the chroot direcory mounted NFS or a "make world" with /usr/obj mounted NFS (I patched /sys/nfs/nfs_vnops.c not return an error on "chflags" system calls), cap_mkdb determinstically dumps core while processing termcap: ===> share/termcap ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > /dev/ null cap_mkdb termcap *** Signal 11 This only happens with NFS v3, not NFS v2 - If the shell output (e.g. for tcsh and XFree86 "make World >&! World.log) is on an NFS mounted drive, and I watch the file with less (less World.log) go to the end of file (Shift-G), sometimes the output gets filled up with 0 characters. This happens with both NFS v2 and v3. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message