From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Jim Rees <rees@umich.edu>
Cc: linux-nfs@vger.kernel.org, peter honeyman <honey@citi.umich.edu>
Subject: Re: state manager failed on NFSv4 server
Date: Wed, 12 Jan 2011 14:13:36 -0500 [thread overview]
Message-ID: <1294859616.2971.46.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20110112185843.GA14207@merit.edu>
On Wed, 2011-01-12 at 13:58 -0500, Jim Rees wrote:
> A kernel built from Benny's pnfs-all-latest can no longer mount the EMC
> server because nfs4_state_manager() fails. I suspect it doesn't like
> something about the EXCHANGE_ID reply. This worked before Benny's last
> update (late Dec?), and I can bisect if necessary, but wondered if someone
> here can take a look and see if there is something obviously wrong.
>
> I put a dump of the call and reply here:
> http://www.citi.umich.edu/projects/nfsv4/pnfs/block/emc-ng-state-mgr
>
> I can of course provide more info if that would help.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
That is correct. According to your wireshark dump, your server is
returning an illegal combination of the EXCHGID4_FLAG_USE_* flags.
The combination
(EXCHGID4_FLAG_USE_PNFS_MDS | EXCHGID4_FLAG_USE_PNFS_DS |
EXCHGID4_FLAG_USE_NON_PNFS)
is not listed in the table in section 13.1 of RFC5661 as an acceptable
return value.
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-01-12 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 18:58 state manager failed on NFSv4 server Jim Rees
2011-01-12 19:13 ` Trond Myklebust [this message]
2011-01-13 0:07 ` Jim Rees
2011-01-13 0:18 ` Trond Myklebust
2011-01-13 0:30 ` Jim Rees
2011-01-13 0:37 ` Trond Myklebust
2011-01-13 0:54 ` Jim Rees
2011-01-13 13:23 ` Benny Halevy
2011-01-12 19:15 ` Andy Adamson
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=1294859616.2971.46.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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