On Thu, Apr 10, 2003 at 05:02:25PM +1000, Daniel Carosone wrote:
> Actually, it changes if i umount and remount after fsck!
> 
> In all this time, fsck says the filesystem is clean (even after
> -f). But there are a different set of files giving this error.
> 
> It looks like the problem is in the kernel reading the fs, more
> likely than in fsck, to me.

I decided I needed to blow away the fs and start again.  I was
prepared to start from a blank /usr and rebuild stuff, but for
curiosity first I did a dump/newfs/restore of /usr first.  This
seems to have worked fine, dump didn't complain about any problems
in the fs, and once restored everything is as it should be (minus
a few files from pkgs that got unlinked by fsck earlier).

So it's clearly a runtime problem.

I'm sorry I couldn't keep the filesystem around for examination
and testing any longer, but I needed a working laptop.

--
Dan.