From: Jesper Krogh <jesper-Q2TZfHgGEy4@public.gmane.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS list <linux-nfs@vger.kernel.org>
Subject: Re: Kernel call trace on NFS-mount (using autofs).
Date: Tue, 20 May 2008 21:31:55 +0200 [thread overview]
Message-ID: <4833272B.9030602@krogh.cc> (raw)
In-Reply-To: <1211311573.23156.10.camel@localhost>
Trond Myklebust wrote:
> That appears to be crashing in generic VFS code rather than in anything
> nfs specific, so I'd suggest reposting this Oops to linux-fsdevel. It
> would be nice if you could first try to reproduce it with 2.6.25,
> though.
Can I safely upgrade kernel to 2.6.25 without changing userspace utils
and autofs?
It is not particulary repoducible. I happens "every second day on a
random node of a set of around 48".
--
Jesper
next prev parent reply other threads:[~2008-05-20 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 18:55 Kernel call trace on NFS-mount (using autofs) Jesper Krogh
[not found] ` <48331EAE.6060107-Q2TZfHgGEy4@public.gmane.org>
2008-05-20 19:26 ` Trond Myklebust
2008-05-20 19:31 ` Jesper Krogh [this message]
[not found] ` <4833272B.9030602-Q2TZfHgGEy4@public.gmane.org>
2008-05-20 19:37 ` Trond Myklebust
2008-05-20 20:28 ` Chuck Lever
2008-05-21 5:03 ` Jesper Krogh
[not found] ` <4833AD1B.6010408-Q2TZfHgGEy4@public.gmane.org>
2008-05-21 16:53 ` Chuck Lever
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=4833272B.9030602@krogh.cc \
--to=jesper-q2tzfhggey4@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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