From owner-freebsd-bugs Sat Jan 2 10:57:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14518 for freebsd-bugs-outgoing; Sat, 2 Jan 1999 10:57:55 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14513 for ; Sat, 2 Jan 1999 10:57:54 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id KAA19337; Sat, 2 Jan 1999 10:57:28 -0800 (PST) Date: Sat, 2 Jan 1999 10:57:28 -0800 (PST) From: Chris Timmons To: Robert Eckardt cc: FreeBSD-bugs@FreeBSD.ORG Subject: Re: kern/9277: NFS-Bug in 3.0 ? In-Reply-To: <199901021539.QAA07822@eckardt.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm afraid that I've pretty much had to resort to '-2' with my mounts in order to get any work done with NFS. A really easy way to reproduce data corruption is to mount /usr/ports via NFS and then on the client side, try building XFree86 or something like that which has huge distfiles. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message