Re: 1.2.9 lockup - more information

Marek Michalkiewicz (
Mon, 3 Jul 1995 12:45:41 +0200 (MET DST)
> I made some testings on the machine and I could reproduce the problem
> by using debugfs. Basically, the problem is due to a filesystem corruption
> which is badly handled in the kernel code and which is not checked by e2fsck.

Quite possible - this system had a filesystem corruption (due to faulty RAM)
about two months before. Some files were suddenly directories, trying to
remove them caused rmdir to hang so that even kill -9 didn't work, etc.
The system was then rebooted and fsck had to be run manually, but it seemed
to fix all problems... SIMMs have been replaced (all four, 4M*9 each, were
bad!) but a rarely accessed directory somewhere on the disk could still be

Thanks again for looking into this problem.