Adrian Head wrote:
> have top running in another console. When the machine hangs - there
are no
> messages in the logs or on screen. The only indication is that there
is no
> disk activity and that top shows that all the cp processes are in "D"
state.
> 9 times out of 10 kupdated is still shown as running in top. - --
> Adrian Head
Interesting thing... Some people (including me) have seen this
myserious
kupdated runnings on smp machines only. Maybe there is something wrong
with
filehandling.. something like that a deadlock occures. I can reproduce
it when I
write to a nearly full xfs. 1% left but only on one of my partitions...
it is
the last one. Another partition which is the first one at the same disc
can be
filled up to 100%. Some people wrote that the problem went away if they
running
a single cpu kernel. Your simple test shows that there is a real problem
with
xfs which should be solved quickly. After such a kupdated amok running
opened
files are filled with @'s and any change or creation of new files are
lost. I
saw this with 2.4.2 / 2.4.5 smp-kernels and with xfs-1.0 / 1.01.
regards
c. radeke
|