> I'm getting errors with directories that turn into files all of a
> sudden. It happened with my /usr/X11R6/lib/X11/fonts/misc so I
> couldn't start X this morning, and today I compiled and installed
> XEmacs, which make .../etc/toolbar/ into a file consisting of SGML.
>
> I tried rm -rf /usr/local/lib/xemacs-20.3/ which had the offending
> toolbar "file", and now the process eats all of my CPU, refusing to
> die.
>
> Running dmesg tells me:
> EXT2-fs warning (device 03:04): ext2_free_blocks: bit already cleared for block 508248
> EXT2-fs warning (device 03:04): ext2_free_blocks: bit already cleared for block 508260
> EXT2-fs warning (device 03:04): empty_dir: bad directory (dir #42990) - no `.' or `..'
>
> I never had problems with 2.0.31 (or any other kernel) until
> recently[1]. What could this be? Hardware failure?
I have had the same experience. I had been running 2.0.31 for about 2 weeks
with no problems. Then I started installing some software and things started
going wacky. In the span of three days I lost my root and fourth partion
about three times, thankfully I had tape backup.
I recieved exaclty the same messages as above except that I lost all my logs
in the corruption. This seems to only happen to device 3:01 and 3:04 for
some reason.
If I tried to decompress and untar a large archive the above would happen but
a lot worse.
My system is a P133 with 32Mb a 3.1 Gig and 170 MB IDE, 300 MB and 80MB SCSI
running off a ah1542cf. All the corruption occurred on my 3.1 gig drive.
I am running with libc-5.3.38 and gcc 2.7.2.3.
I have switch back to 2.0.30 and things seem to be back to normal.
Something is very none kosher in 2.0.31.
ttyl
Dima