From owner-freebsd-current Sat Nov 27 10:17:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id BDFEC14C36 for ; Sat, 27 Nov 1999 10:17:32 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id TAA10347; Sat, 27 Nov 1999 19:17:31 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id TAA53868; Sat, 27 Nov 1999 19:17:30 +0100 (MET) Date: Sat, 27 Nov 1999 19:17:30 +0100 From: Eivind Eklund To: "Viren R.Shah" Cc: freebsd-current@FreeBSD.ORG Subject: Re: repeatable crash in -current (softupdates, NFS) Message-ID: <19991127191729.A53832@bitbox.follo.net> References: <14399.63511.296802.242618@jabberwock.rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14399.63511.296802.242618@jabberwock.rstcorp.com>; from viren@rstcorp.com on Sat, Nov 27, 1999 at 10:26:15AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 27, 1999 at 10:26:15AM -0500, Viren R.Shah wrote: > > I'm running a -current system from Nov 26th (approx 4am EST). > > I can currently reliably crash the system by doing: > > ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html > > > The crash only works when I do it on a NFS mounted filesystem. I'm > using NFSv2/UDP. The server is a 3.2-STABLE FreeBSD box, running > softupdates on the exported filesystem. I just checked that local > filesystem on the server, and it is a 100% full. Can this just be put > down to the known "softupdates full filesystem bug"? > > [BTW: the server hasn't crashed, it's only the FreeBSD client that > crashes] I *think* I know what this is due to - please upgrade src/sys/nfs/nfs_vnops.c to revision 1.146 (which I just committed) and try again. My bad. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message