On Jul 27, 2005, at 3:52 PM, John Summerfied wrote:
Ranga Nathan wrote:
We are running SuSE 9 on a guest under z/VM 5.1. I have been
getting a
message from the cron daemon about a problem with the "updatedb"
script.
On investigation I found that this script file was corrupted at
the end.
My attempts to rsync and edit caused this guest to hang. I had to
re-IPL
it many times. When I deleted this file and tried to rsync it from
another, it hung as I was typing.
I found some file corruptions on the root file system (reiserfs).
I can
not believe that a file corruption could hang Linux. I have never
seen
this happen.
Why on earth not? If linux can't read bits of itself, why would it
not fail?
Well, there's a difference between failing with
Panic: disk_read() failed for block 2439218!
and
Panic: <debugging information containing register contents, followed
by hard system crash>
and just freezing up and refusing to budge.
It sounds like the last--which is the least desirable option--is
what's happening.
Adam
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
