The story begins when I interrupted a "rm -rf /usr/local/lib/" started
by mistake. (as root) Next thing I know I can't compile anything, gcc
dies with signal 11. Well I checked that /usr/local/lib doesn't
contain any files required/used by gcc. Well it shouldn't.
A bit later I had to install a program from CD, I ejected the CD
inserted by that time (wasn't mounted since it was ejected) and an
mount attempt (actually several) on the new CD gave me:
Jan 14 16:45:40 pasuuna kernel: hdc: media changed
Jan 14 16:45:40 pasuuna kernel: hdc : tray open or drive not ready
Jan 14 16:45:42 pasuuna last message repeated 2 times
Jan 14 16:45:43 pasuuna kernel: hdc: media changed
Jan 14 16:45:43 pasuuna kernel: VFS: Disk change detected on device 16:00
Jan 14 16:45:53 pasuuna kernel: hdc: irq timeout: status=0xd0
Jan 14 16:45:53 pasuuna kernel: hdc: ATAPI reset complete
Jan 14 16:45:54 pasuuna kernel: ISO9660 Extensions: Microsoft Joliet Level 1
Jan 14 16:45:54 pasuuna kernel: Max size:308553 Log zone size:2048
Jan 14 16:45:54 pasuuna kernel: First datazone:25 Root inode number 51200
Jan 14 16:45:54 pasuuna kernel: VFS: Disk change detected on device 16:00
Jan 14 16:45:54 pasuuna kernel: VFS: inode busy on removed device 16:00
Jan 14 16:45:54 pasuuna kernel: VFS: inode busy on removed device 16:00
Jan 14 16:45:54 pasuuna kernel: VFS: brelse: Trying to free freebuffer
Jan 14 16:47:25 pasuuna kernel: hdc: media changed
Beyond those messages I couldn't use/mount/umount the drive at all.
After playing a while with it, I gave up since something was definetly
wrong as I couldn't compile anything. I rebooted and everything seems
fine again, I can compile and mount/umount.
Sorry there were no oops, I just thought I let you guys know. Maybe
the rm -rf caused inodes to get corrupted causing havoc? If so, I
still need to come up with a theory for the failing compile because I
use my box for compiling all the time and I wouldn't be much off by
saying that I had compiled something 10 minutes before the rm -rf
incident.
I'm just speculating here but I must admit I have never seen a Linux
box behave this way before. Maybe failing hardware, hmm?
The system is from a clean 2.0.33 tree with the Joliet patch applied,
rm is from fileutils 3.16, the mount is 2.7g and libc is 5.4.38.
-- Samuli Kaski, samkaski@cs.helsinki.fi Department of Computer Science, University of Helsinki, Finland.