From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Jiri Slaby <jirislaby@gmail.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: Fri, 04 Sep 2009 18:53:17 -0400 [thread overview]
Message-ID: <1252104797.5274.19.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <4AA19420.5060503@gmail.com>
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
>
> Thanks.
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.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2009-09-04 22:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 23:40 mmotm 2009-09-03-16-35 uploaded akpm
2009-09-04 12:56 ` Dave Young
2009-09-04 23:17 ` Andrew Morton
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
2009-09-04 22:26 ` Jiri Slaby
2009-09-04 22:53 ` Trond Myklebust [this message]
2009-09-06 16:11 ` Jiri Slaby
2009-09-04 23:30 ` mmotm 2009-09-03-16-35 uploaded Randy Dunlap
2009-09-09 0:49 ` KOSAKI Motohiro
2009-09-09 1:14 ` KAMEZAWA Hiroyuki
2009-09-09 1:31 ` KAMEZAWA Hiroyuki
2009-09-10 1:39 ` KOSAKI Motohiro
2009-09-10 2:58 ` [PATCH][mmotm][BUGFIX] kcore use registered physmem information ia64-fix (Was " KAMEZAWA Hiroyuki
2009-09-11 1:25 ` KOSAKI Motohiro
2009-09-09 1:34 ` KOSAKI Motohiro
2009-09-09 7:35 ` Mel Gorman
2009-09-09 8:17 ` KOSAKI Motohiro
2009-09-09 8:47 ` Mel Gorman
2009-09-09 8:51 ` KOSAKI Motohiro
2009-09-09 9:31 ` Mel Gorman
2009-09-10 0:02 ` KOSAKI Motohiro
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=1252104797.5274.19.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=jirislaby@gmail.com \
--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
all inboxes | Powered by JetHome®