Date: Wed, 10 Mar 2004 19:19:48 +0100 From: Manfred Lotz <manfred.lotz@web.de> To: freebsd-stable@freebsd.org Subject: Re: unexpected softupdate inconsistency Message-ID: <pan.2004.03.10.18.19.42.197648@web.de> References: <pan.2004.03.10.07.27.44.911448@web.de> <1078910490.1333.2.camel@localhost> <20040310112332.76f76bf7.manfred.lotz@web.de> <200403101139.08107.michaelnottebrock@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <msergeant@snsonline.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?pan.2004.03.10.18.19.42.197648>