Date: Wed, 10 Mar 2004 20:40:36 +1000 From: Mark Sergeant <msergeant@snsonline.net> To: Manfred Lotz <manfred.lotz@web.de> Cc: freebsd-stable@freebsd.org Subject: Re: unexpected softupdate inconsistency Message-ID: <1078915236.1333.5.camel@localhost> In-Reply-To: <20040310112332.76f76bf7.manfred.lotz@web.de> References: <pan.2004.03.10.07.27.44.911448@web.de> <1078910490.1333.2.camel@localhost> <20040310112332.76f76bf7.manfred.lotz@web.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-YneGad4k+LGvdib4pfN9 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-03-10 at 20:23, Manfred Lotz wrote: > On Wed, 10 Mar 2004 19:21:30 +1000 > Mark Sergeant <msergeant@snsonline.net> wrote: >=20 > > 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. > >=20 > > Cheers, > >=20 > > Mark >=20 > Thanks for the reply. Have to admit that it would have never occured to > me to do this. Good idea. >=20 > Did you experience this often? I'm worried. Never had something like > this before. Had it happen twice before on my laptop running current, editing the dir in the ports work dir worked both times. The reason was due to the compile going plus a bunch of other scripts generating high IO when the battery died (oops ;)). Cheers, Mark >=20 >=20 > Manfred >=20 > >=20 > > On Wed, 2004-03-10 at 17:27, Manfred Lotz wrote: > > > Hi there, > > > System is FreeBSD 4.9 Stable > > >=20 > > > Had a problem during a portupgrade that when portupgrade did some > > > cleaning a directory could not be deleted because it were not empty. > > > However, it was empty. rm -rf didn't help either. > > >=20 > > > Because I didn't know what to do I decided to boot. > > >=20 > > > At system startup fsck was started which produced the message: > > > unexpected softupdate inconsistency and also that some blocks could > > > not be written to. At the end fsck said: filesystem still dirty and > > > I should run fsck manually which I did but without any success. > > >=20 > > > After that I rebooted from CD and did two backups of the filesystem > > > using dump and tar. Both commands complained at the locations where > > > the file system was corrupt but the backup went fine besides that. > > >=20 > > > I checked for hardware errors by running > > > dd if=3D/dev/ad0s1g of=3D/dev/null bs=3D32k=20 > > > Ran fine without any complains. > > >=20 > > > After recreating the filesystem with newfs and restoring the data > > > I'm fine for now. > > >=20 > > > I should mention that I did not find any related messages in > > > /var/log/messages. > > >=20 > > >=20 > > > However, I'm really worried. Is there anybody I could do??? --=20 Mark Sergeant <msergeant@snsonline.net> SNSOnline Technical Services --=-YneGad4k+LGvdib4pfN9 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBATvCkbS4ZEpHb8t0RAqcIAJ0ahNCJ/6JuW5JULr6H0DohFlBsSACfaVJv vClboiP2QIjZ7gQ4BoSJW6s= =wzJZ -----END PGP SIGNATURE----- --=-YneGad4k+LGvdib4pfN9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1078915236.1333.5.camel>