From: Jiri Slaby <jirislaby@gmail.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-nfs@vger.kernel.org
Subject: Re: mount.nfs oops [was: mmotm 2009-09-03-16-35 uploaded]
Date: Sun, 06 Sep 2009 18:11:03 +0200 [thread overview]
Message-ID: <4AA3DF17.2000401@gmail.com> (raw)
In-Reply-To: <1252104797.5274.19.camel@heimdal.trondhjem.org>
On 09/05/2009 12:53 AM, Trond Myklebust wrote:
> On Sat, 2009-09-05 at 00:26 +0200, Jiri Slaby wrote:
>> On 09/05/2009 12:12 AM, Trond Myklebust wrote:
>>> Also, were you doing anything special at the time (for instance removing
>>> a module)?
>>
>> Not at all. I just did
>> # mount /work
>> # grep work /etc/fstab
>> XXX.YYY.ZZZ:/work /work nfs defaults,intr 0 0
>>
> Hmm... Is it fully reproducible? I'm running the same NFS client code
> (although not the full linux-mm) on several different client platforms
> without seeing any issues.
I saw this only twice on the same bootup. I can't reproduce on demand,
sorry.
prev parent reply other threads:[~2009-09-06 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909032340.n83Ne6E6004708@imap1.linux-foundation.org>
[not found] ` <200909032340.n83Ne6E6004708-AB4EexQrvXRQetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
2009-09-04 20:54 ` mount.nfs oops [was: mmotm 2009-09-03-16-35 uploaded] Jiri Slaby
2009-09-04 22:12 ` Trond Myklebust
[not found] ` <1252102337.5274.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-09-04 22:26 ` Jiri Slaby
2009-09-04 22:53 ` Trond Myklebust
2009-09-06 16:11 ` Jiri Slaby [this message]
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=4AA3DF17.2000401@gmail.com \
--to=jirislaby@gmail.com \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mm-commits@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;
as well as URLs for NNTP newsgroup(s).