First number one went down, with a real, honest-to-goodness hardware
failure, half the scsi drives went west. Then my day went downhill.
Number two spontaneously rebooted while I was in transit to the site,
and came up in run-level 2 then produced a panic: FORWARDED INTERRUPT
TIMEOUT.
Deep breath. Okay. The day is likely to only get better after this.
Right? Wrong.
Within the next hour, number three and number four go down almost
simultaneously with: "VFS: No free inodes - contact Linus"
Well..I felt damn sure that Linus was too busy to bother. I know I was
too busy fighting the problems to do much about it, but now that it's
late at night and I'm finally back home for my first coffee of the day
and a little breakfast, I am moved to ask: Does anyone know what the
heck caused the above, and what might be a good method of avoiding it?
The kernels themselves are unremarkable: 2.0.32+SMP+3000fd.
D
-- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GAT d- s++: a C++++$ UL++++B+++S+++C++H++U++V+++$ P+++$ L+++ E- W+++(--)$ N++ w++$>--- t+ 5++ X+() R+ tv b++++ DI+++ e- h-@ ------END GEEK CODE BLOCK------- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html