All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Posonsky <psk@cpositive.ru>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Error: state manager failed on NFSv4 server base with error 10018
Date: Thu, 22 Sep 2011 11:42:25 +0900	[thread overview]
Message-ID: <201109221142.25798.psk@cpositive.ru> (raw)
In-Reply-To: <20110921160020.GD21510@fieldses.org>

[-- Attachment #1: Type: Text/Plain, Size: 2332 bytes --]

On Thursday 22 of September 2011 01:00:20 you wrote:
> On Wed, Sep 21, 2011 at 01:34:34PM +0900, Stanislav Posonsky wrote:
> > 	After upgrade kernel at server from 2.6.38 to 2.6.39 series and higher,
> > 
> > I was forced to drop to NFSv3. With NFSv4 I get (when I trying to read
> > any
> > 
> > file) hundreds message at client:
> > 	Error: state manager failed on NFSv4 server base with error 10018
> > 	
> > 	Now I have at server and cient:
> > 	
> > 	linux kernel 	3.0.4
> > 	nfs-utils		1.2.3
> > 	nfs4-acl-tools	0.3.3
> > 
> > 	File /etc/exports:
> > /opt                        192.168.8.0/24(fsid=0,rw,subtree_check)
> > 
> > ==================================================
> > 
> > 	With version 3
> > 
> > ==================================================
> > 
> > root|st01# mount -t nfs -o nfsvers=3 base:/opt /net
> > root|st01# mount | grep nfs
> > rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> > base:/opt on /net type nfs (rw,nfsvers=3,addr=192.168.8.254)
> > 
> > 	In other console:
> > stas@st01$ ls -l /net/a*
> > -rw-r--r-- 1 root root 35 Сен 21 11:23 /net/a_file.txt
> > stas@st01$ cat /net/a_file.txt
> > This is a test file on NFS share.
> > 
> > stas@st01$
> > 
> > 	Works fine.
> > 
> > ==================================================
> > 
> > 	With version 4
> > 
> > ==================================================
> > 
> > root|st01# umount /net
> > root|st01# mount -t nfs base:/ /net
> > root|st01# mount | grep nfs
> > rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> > base:/ on /net type nfs
> > (rw,vers=4,addr=192.168.8.254,clientaddr=192.168.8.1)
> > 
> > 	In other console:
> > stas@st01$ ls -l /net/a*
> > -rw-r--r-- 1 root root 35 Сен 21 11:23 /net/a_file.txt
> > stas@st01$ cat /net/a_file.txt
> > 
> > 	And the process hangs... Then (Ctl+C):
> > ^C
> > stas@st01$ dmesg
> > Error: state manager failed on NFSv4 server base with error 10018
> > Error: state manager failed on NFSv4 server base with error 10018
> > ...
> > 
> > Could you help me solve this problem, please?
> 
> Could you get a network trace showing the "With version 4" case?
> 
> (tcpdump -s0 -wtmp.pcap, then run your test, then kill tcpdump and mail
> me tmp.pcap)

	Yes, certainly. Two files are in attachment - at "mount" and "cat" 
stages.
-- 
  With best regards, Stanislav

[-- Attachment #2: mount.pcap --]
[-- Type: application/octet-stream, Size: 5194 bytes --]

[-- Attachment #3: cat.pcap --]
[-- Type: application/octet-stream, Size: 42108 bytes --]

  reply	other threads:[~2011-09-22  2:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21  4:34 Error: state manager failed on NFSv4 server base with error 10018 Stanislav Posonsky
2011-09-21 16:00 ` J. Bruce Fields
2011-09-22  2:42   ` Stanislav Posonsky [this message]
2011-12-08 21:52     ` J. Bruce Fields

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=201109221142.25798.psk@cpositive.ru \
    --to=psk@cpositive.ru \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.