From owner-freebsd-current Wed May 2 3:39: 6 2001 Delivered-To: freebsd-current@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 6802537B422 for ; Wed, 2 May 2001 03:39:04 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 14uu2A-00083r-0K; Wed, 2 May 2001 10:39:02 +0000 Received: from herring (herring [10.0.0.2]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f42Abk754391; Wed, 2 May 2001 11:37:46 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 2 May 2001 11:37:45 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: Subject: Re: HEADS UP! bad bug in -current. In-Reply-To: <20010501191534.96E1A380C@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 May 2001, Peter Wemm wrote: > Any -current kernel built over the weekend is a likely victim of this bug. > In a nutshell, it will eat your root filesystem at the very least, leaving > you with maybe one or two files in /lost+found. spec_vnops.c rev 1.156 > is should be avoided at all costs. > > BEWARE: there are some snapshots on current.freebsd.org with this bug. They > will self destruct after install. Too late - I'm just rebuilding one of my scratch machines right now :-( -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message