From owner-freebsd-stable@FreeBSD.ORG Wed Mar 10 11:09:15 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 902D016A4CE for ; Wed, 10 Mar 2004 11:09:15 -0800 (PST) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id E00AC43D46 for ; Wed, 10 Mar 2004 11:09:14 -0800 (PST) (envelope-from freebsd-stable@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1B194r-0001bY-00 for ; Wed, 10 Mar 2004 20:09:13 +0100 Received: from dsl-082-083-134-168.arcor-ip.net ([82.83.134.168]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Mar 2004 20:09:13 +0100 Received: from manfred.lotz by dsl-082-083-134-168.arcor-ip.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 10 Mar 2004 20:09:13 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Manfred Lotz Date: Wed, 10 Mar 2004 19:19:48 +0100 Lines: 30 Message-ID: References: <1078910490.1333.2.camel@localhost> <20040310112332.76f76bf7.manfred.lotz@web.de> <200403101139.08107.michaelnottebrock@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: dsl-082-083-134-168.arcor-ip.net User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) Sender: news Subject: Re: unexpected softupdate inconsistency X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2004 19:09:15 -0000 On Wed, 10 Mar 2004 11:39:07 +0100, Michael Nottebrock wrote: > On Wednesday 10 March 2004 11:23, Manfred Lotz wrote: >> On Wed, 10 Mar 2004 19:21:30 +1000 >> >> Mark Sergeant wrote: >> > In situations like this it can be useful to use vim on the dir entry >> > that is affected and remove the invalid filenames. This has worked for >> > me before. >> > >> > Cheers, >> > >> > Mark >> >> Thanks for the reply. Have to admit that it would have never occured to >> me to do this. Good idea. >> >> Did you experience this often? I'm worried. Never had something like >> this before. > > You should watch that system - filesystems going bad out of the blue are > usually a warning sign of failing hardware (though not necessarily the hdd > itself, might be power issues, bad memory, etc.). Thanks, I'll have my eye on it. Unpleasant situation anyhow. -- Manfred