From owner-freebsd-stable@FreeBSD.ORG  Wed Mar 10 02:39:14 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 90D1E16A4CE; Wed, 10 Mar 2004 02:39:14 -0800 (PST)
Received: from meitner.wh.uni-dortmund.de (meitner.wh.uni-dortmund.de
	[129.217.129.133])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4E97443D2F; Wed, 10 Mar 2004 02:39:14 -0800 (PST)
	(envelope-from michaelnottebrock@gmx.net)
Received: from lofi.dyndns.org (pc2-105.intern.meitner [10.3.12.105])
	by meitner.wh.uni-dortmund.de (Postfix) with ESMTP
	id 8382F167522; Wed, 10 Mar 2004 11:39:13 +0100 (CET)
Received: from [192.168.8.4] (kiste.my.domain [192.168.8.4])
	(authenticated bits=0)
	by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id i2AAd8kJ035009
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Wed, 10 Mar 2004 11:39:09 +0100 (CET)
	(envelope-from michaelnottebrock@gmx.net)
From: Michael Nottebrock <michaelnottebrock@gmx.net>
To: stable@freebsd.org
Date: Wed, 10 Mar 2004 11:39:07 +0100
User-Agent: KMail/1.6
References: <pan.2004.03.10.07.27.44.911448@web.de>
	<1078910490.1333.2.camel@localhost>
	<20040310112332.76f76bf7.manfred.lotz@web.de>
In-Reply-To: <20040310112332.76f76bf7.manfred.lotz@web.de>
MIME-Version: 1.0
Content-Type: multipart/signed;
  protocol="application/pgp-signature";
  micalg=pgp-sha1;
  boundary="Boundary-02=_MBvTAQdkBvJ1uRn";
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200403101139.08107.michaelnottebrock@gmx.net>
X-Virus-Scanned: by amavisd-new
cc: freebsd-stable@freebsd.org
cc: Manfred Lotz <manfred.lotz@web.de>
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
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2004 10:39:14 -0000


--Boundary-02=_MBvTAQdkBvJ1uRn
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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=20
usually a warning sign of failing hardware (though not necessarily the hdd=
=20
itself, might be power issues, bad memory, etc.).

=2D-=20
   ,_,   | Michael Nottebrock               | lofi@freebsd.org
 (/^ ^\) | FreeBSD - The Power to Serve     | http://www.freebsd.org
   \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org

--Boundary-02=_MBvTAQdkBvJ1uRn
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQBATvBMXhc68WspdLARAh6zAJwLFN8PEJpZ41HxZmvtLYsMHTnYZQCeOTj3
+rpTw5ArWPQ/wTr+xS+QbMg=
=Wne0
-----END PGP SIGNATURE-----

--Boundary-02=_MBvTAQdkBvJ1uRn--