On Sun, Feb 02, 2003 at 01:36:03PM -0800, Paul Hoffman wrote:
> Thanks for all the help so far. It is indeed that the bad-sector file 
> is already full, and spilling over. So I have backed up the important 
> parts of this drive, and have a new drive on order. The system is 
> limping along in an interesting fashion. It works fine for about 48 
> hours with no messages like the one above, then gets pretty damn 
> stuck emitting messages like the one above. Sometimes I can do a 
> clean reboot, sometimes I can't, and even 'fsck -y' in single-user 
> mode gets a bit haired out.
> 
> So, my question is this: can I determine what files are associated 
> with the error messages? If they are files that get accessed but I 

Well, currently there's no such tool, as fast as I know, but I guess
writing one from fsck/fsdb shouldn't be too hard.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 24 ans d'experience feront toujours la difference
--