From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Steinar Hauan <hauan@cmu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17smp kernel oops in nfs client
Date: 20 Jan 2002 19:17:54 +0100 [thread overview]
Message-ID: <shs7kqc6g4t.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.GSO.4.43L-024.0201191310210.4325-700000@unix1.andrew.cmu.edu>
In-Reply-To: <Pine.GSO.4.43L-024.0201191310210.4325-700000@unix1.andrew.cmu.edu>
>>>>> " " == Steinar Hauan <hauan@cmu.edu> 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
next prev parent reply other threads:[~2002-01-20 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 18:18 Steinar Hauan
2002-01-20 18:17 ` Trond Myklebust [this message]
2002-01-21 14:26 ` Steinar Hauan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=shs7kqc6g4t.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=hauan@cmu.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®