From owner-freebsd-current Mon Nov 29 7: 8:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id E9A2115033 for ; Mon, 29 Nov 1999 07:08:32 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991127195332.36233@mojave.sitaranetworks.com> Date: Sat, 27 Nov 1999 19:53:32 -0500 From: Greg Lehey To: "Viren R.Shah" , freebsd-current@FreeBSD.ORG Subject: Re: repeatable crash in -current (softupdates, NFS) Reply-To: Greg Lehey References: <14399.63511.296802.242618@jabberwock.rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <14399.63511.296802.242618@jabberwock.rstcorp.com>; from Viren R.Shah on Sat, Nov 27, 1999 at 10:26:15AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 27 November 1999 at 10:26:15 -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"? Not based on the (non-existent) evidence you've supplied. Where does it crash? > [BTW: the server hasn't crashed, it's only the FreeBSD client that > crashes] Do you mean the client process or the client operating system? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message