" Basically, the problem is due to a filesystem corruption
which is badly handled in the kernel code and which is not checked by
e2fsck. "
Yes, I know most of the kernel hacking effort is being expended on 1.3.x
right now, but there's a fair number of us hanging back at the 1.2.x
point. It just gives me a bit of an uneasy feeling, knowing there's an
identified bug waiting to do nasty things to my filesystem.
Something else occurred the other day. I telnet'd in to my machine,
Did an 'ls -a' of a directory on a mounted filesystem. The listing hung
part way through. Since my machine is connected to the net via a ppp
connection, I had to wait till I got home that night to see what had
happened. Screen was blank, ppp connection had dropped (probably due to
time-out from my provider's annex server), but DTR light on the modem was
still lit (isn't when I shut ppp down gracefully). System was totally
locked. Could not change v.c.'s, and since screen was totally blank,
couldn't tell if there had been any panic messages. Had to mash the
reset button. No messages in the syslogs at all at the time of the crash.
I suspect this might be one of the 'lock-ups' I've seen several
references to lately, but fortunately no damage was done to the file
system.
Will there be another 1.2.x that addresses the remaining problems ?
__
********************************************************************************
_/_/_/_/_/ _/_/_/_/_/ _/_/_/_/_/ _/ _/ | Gary Anderson
_/ _/ _/ _/ _/ _/ _/ | ganderson@clark.net
_/ _/_/_/ _/_/_/_/_/ _/_/_/_/_/ _/_/ | --------------------
_/ _/ _/ _/ _/ _/ _/ | finger me for my
_/_/_/_/_/ _/ _/ _/ _/ _/ | pgp public key
********************************************************************************
The only thing to do with good advice is pass it on. It is never any
use to oneself.
-- Oscar Wilde