2002-01-19 18:18:51

by Steinar Hauan

[permalink] [raw]
Subject: 2.4.17smp kernel oops in nfs client

hello,

log monitoring revealed that a user processed crashed a few days
ago and left an ooops message along with a zombie user process
(in non-interruptible disk wait).

the machine was still running fine with +2 extra load.

ksymoops output attached along with other details.

regards,
--
Steinar Hauan, dept of ChemE -- [email protected]
Carnegie Mellon University, Pittsburgh PA, USA


Attachments:
ksymops.txt (2.90 kB)
proc-modules.txt (258.00 B)
ver_linux.txt (631.00 B)
lspci.txt (3.79 kB)
proc-cpuinfo.txt (804.00 B)
kernel-version.txt (125.00 B)
Download all attachments

2002-01-20 18:18:19

by Trond Myklebust

[permalink] [raw]
Subject: Re: 2.4.17smp kernel oops in nfs client

>>>>> " " == Steinar Hauan <[email protected]> writes:

> hello,
> log monitoring revealed that a user processed crashed a few
> days ago and left an ooops message along with a zombie user
> process (in non-interruptible disk wait).

Hi,
Did you find any other NFS related messages in your syslog? Short of
a bug in truncate_inode_pages(), I really can't see how this could
happen. Certainly whatever is was should at least have triggered a
couple of NFS warnings...

Cheers,
Trond

2002-01-21 14:27:16

by Steinar Hauan

[permalink] [raw]
Subject: Re: 2.4.17smp kernel oops in nfs client

On 20 Jan 2002, Trond Myklebust wrote:
> >>>>> " " == Steinar Hauan <[email protected]> writes:
>
> > hello,
> > log monitoring revealed that a user processed crashed a few
> > days ago and left an ooops message along with a zombie user
> > process (in non-interruptible disk wait).
>
> Did you find any other NFS related messages in your syslog? Short of
> a bug in truncate_inode_pages(), I really can't see how this could
> happen. Certainly whatever is was should at least have triggered a
> couple of NFS warnings...

there are no nfs error or warning messages at all on either the server
or the client for one week prior to the crash. this includes logs created
by kern.* and *.debug entries in syslog.conf.

regards,
--
Steinar Hauan, dept of ChemE -- [email protected]
Carnegie Mellon University, Pittsburgh PA, USA