linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	mm-commits@vger.kernel.org, ML netdev <netdev@vger.kernel.org>,
	linux-nfs@vger.kernel.org
Subject: Re: nfs client doesn't work [was: mmotm 2011-03-31-14-48 uploaded]
Date: Thu, 07 Apr 2011 08:42:17 +0200	[thread overview]
Message-ID: <4D9D5CC9.2040002@suse.cz> (raw)
In-Reply-To: <1302122693.16786.0.camel@lade.trondhjem.org>

On 04/06/2011 10:44 PM, Myklebust, Trond wrote:
> On Sat, 2011-04-02 at 10:56 +0200, Jiri Slaby wrote:
>> On 03/31/2011 11:48 PM, akpm@linux-foundation.org wrote:
>> > The mm-of-the-moment snapshot 2011-03-31-14-48 has been uploaded to
>>
>> Hi, nfs client is defunct in this kernel. Tcpdump says:
>> 10:51:55.489717 IP 10.20.11.33.759945860 > 10.20.3.2.2049: 132 getattr
>> fh 0,0/24
>> 10:51:55.515927 IP 10.20.3.2.2049 > 10.20.11.33.759945860: reply ok 44
>> getattr ERROR: Operation not permitted
>> 10:51:55.515949 IP 10.20.11.33.921 > 10.20.3.2.2049: Flags [.], ack
>> 3569361440, win 115, options [nop,nop,TS val 599750 ecr 255058541],
> length 0
>> 10:52:04.130310 IP 10.20.11.33.793500292 > 10.20.3.2.2049: 76 getattr fh
>> 0,0/24
>> 10:52:04.152178 IP 10.20.3.2.2049 > 10.20.11.33.793500292: reply ok 44
>> getattr ERROR: Operation not permitted
>>
>> If I run the same mount command (mount -oro,intr host:dir mountpoint)
>> from within a virtual machine with 2.6.38.2 there, everything mounts OK.
> 
> Does the attached patch help?

No, still the operation not permitted in the tcpdump output and no mount.

thanks,
-- 
js
suse labs

  parent reply	other threads:[~2011-04-07  6:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201103312224.p2VMOA5g000983@imap1.linux-foundation.org>
2011-04-02  8:56 ` nfs client doesn't work [was: mmotm 2011-03-31-14-48 uploaded] Jiri Slaby
     [not found]   ` <1302122693.16786.0.camel@lade.trondhjem.org>
2011-04-07  6:42     ` Jiri Slaby [this message]
2011-04-11 20:40       ` Jiri Slaby
2011-04-11 20:40         ` Jiri Slaby
2011-04-11 21:08           ` Jiri Slaby
2011-04-12 17:41             ` [PATCH] NFS: Fix infinite loop in gss_create_upcall() Bryan Schumaker
2011-04-12 18:05               ` Jiri Slaby
2011-04-12 18:31                 ` Trond Myklebust
2011-04-12 18:34                   ` Jiri Slaby
2011-04-12 18:38                     ` Trond Myklebust
2011-04-12 18:43                     ` Bryan Schumaker
2011-04-12 18:52                       ` Jiri Slaby
2011-04-13 20:42                         ` Bryan Schumaker
2011-04-14 20:37                           ` Jiri Slaby
2011-04-14 21:21                             ` Trond Myklebust
2011-04-14 21:30                               ` Jiri Slaby
2011-04-11 20:56         ` nfs client doesn't work [was: mmotm 2011-03-31-14-48 uploaded] Bryan Schumaker
2011-04-11 21:19           ` Jiri Slaby

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=4D9D5CC9.2040002@suse.cz \
    --to=jslaby@suse.cz \
    --cc=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 \
    --cc=netdev@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).