From owner-freebsd-stable@FreeBSD.ORG Wed Mar 10 07:10:35 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 CFD4C16A4CE for ; Wed, 10 Mar 2004 07:10:35 -0800 (PST) Received: from mercury.jorsm.com (mercury.jorsm.com [66.170.168.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B85F43D46 for ; Wed, 10 Mar 2004 07:10:35 -0800 (PST) (envelope-from steveb@mercury.jorsm.com) Received: from localhost (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id F17B21E18A8 for ; Wed, 10 Mar 2004 09:10:34 -0600 (CST) Received: from mercury.jorsm.com (localhost [127.0.0.1]) by localhost (VaMailArmor-2.0.1.16) id 45861-72FD47A3; Wed, 10 Mar 2004 09:10:34 -0600 Received: by mercury.jorsm.com (Postfix, from userid 4147) id D43FC1E189E; Wed, 10 Mar 2004 09:10:34 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by mercury.jorsm.com (Postfix) with ESMTP id D0AAA1E1893 for ; Wed, 10 Mar 2004 09:10:34 -0600 (CST) Date: Wed, 10 Mar 2004 09:10:34 -0600 (CST) From: Stephen Bader To: stable@freebsd.org In-Reply-To: <200403101139.08107.michaelnottebrock@gmx.net> Message-ID: <20040310090937.Y37786-100000@mercury.jorsm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.24.0.6; VDF: 6.24.0.47; host: jorsm.com) 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 15:10:35 -0000 Just for my information if I ever run into this in the future, what do you mean by 'use vim on the dir entry'? -Steve ------------------------------------------------------------------------- Stephen Bader JORSM Internet, Regional Internet Services Systems Administrator 7 Area Codes in Chicagoland and NW Indiana steveb@jorsm.com 100Mbps+ Connectivity, 56K-DS3, V.90, ISDN (219) 322-2180 Quality Service, Affordable Prices http://www.jorsm.com Serving Gov, Biz, Indivds Since 1995 ------------------------------------------------------------------------- On Wed, 10 Mar 2004, 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.). > > -- > ,_, | Michael Nottebrock | lofi@freebsd.org > (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org > \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org >