unexpected softupdate inconsistency

Stephen Bader steveb at mercury.jorsm.com
Wed Mar 10 07:10:35 PST 2004


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 at 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 <msergeant at 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.).
>
> --
>    ,_,   | Michael Nottebrock               | lofi at freebsd.org
>  (/^ ^\) | FreeBSD - The Power to Serve     | http://www.freebsd.org
>    \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org
>



More information about the freebsd-stable mailing list