unexpected softupdate inconsistency

[Mark Sergeant]

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

On Wed, 2004-03-10 at 17:27, Manfred Lotz wrote:
> Hi there,
> System is FreeBSD 4.9 Stable
> 
> 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.
> 
> Because I didn't know what to do I decided to boot.
> 
> 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.
> 
> 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.
> 
> I checked for hardware errors by running
> 	dd if=/dev/ad0s1g of=/dev/null bs=32k 
> Ran fine without any complains.
> 
> After recreating the filesystem with newfs and restoring the data I'm fine
> for now.
> 
> I should mention that I did not find any related messages in
> /var/log/messages.
> 
> 
> However, I'm really worried. Is there anybody I could do???
-- 
Mark Sergeant <msergeant at snsonline.net>
SNSOnline Technical Services
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040310/a60cf148/attachment.bin