state recovery failed on NFSv4 server with error 2
J. Bruce Fields
bfields at fieldses.org
Thu Mar 27 09:46:37 EDT 2008
On Thu, Mar 27, 2008 at 02:15:20AM -0400, Thomas Garner wrote:
> Thanks, Benjamin, for looking into this.
>
> > You may have a poorly behaved server? Any debug from there? Tried a
> > network capture while this happens?
>
> Hopefully not a poorly behaved server since it's OpenSolaris and Sun's nfsd
> (perhaps it's not a guaranteed assumption that Sun has the best nfs
> implementation?). I'm not exactly sure what you're looking for in a packet
> dump, but here's a tcpcdump from the client (192.168.0.99) to the server (
> 192.168.0.10), when Linux is throwing the error. I have the full hex dump
> from the client and a snoop dump from the server, so let me know if you'd
> prefer more/different dumps.
Yeah, there's not quite enough information here. What I usually ask
people to do is run something like
tcpdump -s0 -wtmp.pcap
(and add whatever filter might help get just the nfsv4 traffic) and then
send me tmp.pcap.
--b.
> 01:22:35.043981 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 2529206211
> win 47784 <nop,nop,timestamp 17427540 21670900>
> 01:22:35.044072 IP 192.168.0.10.2049 > 192.168.0.99.607590372: reply ok 56
> 01:22:35.044188 IP 192.168.0.99.691476452 > 192.168.0.10.2049: 1448 getattr
> fh 0,0/22
> 01:22:35.044196 IP 192.168.0.99.1954115685 > 192.168.0.10.2049: 1448
> proc-1634886504
> 01:22:35.044203 IP 192.168.0.99.1953703521 > 192.168.0.10.2049: 1448
> proc-1046836323
> 01:22:35.044208 IP 192.168.0.99.543255660 > 192.168.0.10.2049: 1448
> proc-1953066862
> 01:22:35.044214 IP 192.168.0.99.1914846835 > 192.168.0.10.2049: 1448
> proc-1042294894
> 01:22:35.044220 IP 192.168.0.99.1835284020 > 192.168.0.10.2049: 1168
> proc-1886353253
> 01:22:35.044303 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 4345 win
> 43440 <nop,nop,timestamp 17427540 21670900>
> 01:22:35.044399 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 6961 win
> 49232 <nop,nop,timestamp 17427540 21670900>
> 01:22:35.044500 IP 192.168.0.10.2049 > 192.168.0.99.624367588: reply ok 56
> 01:22:35.044528 IP 192.168.0.10.2049 > 192.168.0.99.641144804: reply ok 56
> 01:22:35.044570 IP 192.168.0.99.708253668 > 192.168.0.10.2049: 1448 getattr
> fh 0,0/22
> 01:22:35.044576 IP 192.168.0.99.1685415200 > 192.168.0.10.2049: 1448
> proc-1701671722
> 01:22:35.044582 IP 192.168.0.99.975203951 > 192.168.0.10.2049: 1448
> proc-1936026725
> 01:22:35.044588 IP 192.168.0.99.2064255332 > 192.168.0.10.2049: 1448
> proc-170093669
> 01:22:35.044594 IP 192.168.0.99.540024880 > 192.168.0.10.2049: 1448
> proc-1886920819
> 01:22:35.044599 IP 192.168.0.99.1179004976 > 192.168.0.10.2049: 1168
> proc-1667591796
> 01:22:35.044607 IP 192.168.0.99.725030884 > 192.168.0.10.2049: 196 getattr
> fh 0,0/22
> 01:22:35.044692 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 10053 win
> 46336 <nop,nop,timestamp 17427540 21670900>
> 01:22:35.044797 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 12949 win
> 43440 <nop,nop,timestamp 17427540 21670900>
> 01:22:35.045565 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 15565 win
> 49232 <nop,nop,timestamp 17427540 21670900>
> 01:22:35.045620 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 18461 win
> 46336 <nop,nop,timestamp 17427540 21670900>
> 01:22:35.045730 IP 192.168.0.10.2049 > 192.168.0.99.657922020: reply ok 56
> 01:22:35.045747 IP 192.168.0.10.2049 > 192.168.0.99.674699236: reply ok 56
> 01:22:35.045790 IP 192.168.0.99.741808100 > 192.168.0.10.2049: 1448 getattr
> fh 0,0/22
> 01:22:35.045796 IP 192.168.0.99.946544749 > 192.168.0.10.2049: 1448
> proc-1885544563
> 01:22:35.045802 IP 192.168.0.99.842413105 > 192.168.0.10.2049: 1448
> proc-1852272425
> 01:22:35.045808 IP 192.168.0.99.775696225 > 192.168.0.10.2049: 1448
> proc-1752462448
> 01:22:35.045813 IP 192.168.0.99.1485393161 > 192.168.0.10.2049: 1448
> proc-2833983756
> 01:22:35.045827 IP 192.168.0.99.1140865536 > 192.168.0.10.2049: 1168
> proc-1811966976
> 01:22:35.045836 IP 192.168.0.99.758585316 > 192.168.0.10.2049: 1448 getattr
> fh 0,0/22
> 01:22:35.045842 IP 192.168.0.99.1718578804 > 192.168.0.10.2049: 1448
> proc-174144108
> 01:22:35.045848 IP 192.168.0.99.1952981091 > 192.168.0.10.2049: 1416
> proc-1852272425
> 01:22:35.045885 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 22773 win
> 46336 <nop,nop,timestamp 17427540 21670901>
> 01:22:35.046034 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 25669 win
> 43440 <nop,nop,timestamp 17427540 21670901>
> 01:22:35.046209 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 28285 win
> 49232 <nop,nop,timestamp 17427540 21670901>
> 01:22:35.046261 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 31181 win
> 46336 <nop,nop,timestamp 17427540 21670901>
> 01:22:35.046294 IP 192.168.0.10.2049 > 192.168.0.99.691476452: reply ok 56
> getattr ERROR: unk 10011
> 01:22:35.046347 IP 192.168.0.99.775362532 > 192.168.0.10.2049: 1448 getattr
> fh 0,0/22
> 01:22:35.046353 IP 192.168.0.99.1954115685 > 192.168.0.10.2049: 1448
> proc-1634886504
> 01:22:35.046359 IP 192.168.0.99.1953703521 > 192.168.0.10.2049: 1448
> proc-1046836323
> 01:22:35.046365 IP 192.168.0.99.543255660 > 192.168.0.10.2049: 1448
> proc-1953066862
> 01:22:35.046370 IP 192.168.0.99.1914846835 > 192.168.0.10.2049: 1448
> proc-1042294894
> 01:22:35.046377 IP 192.168.0.99.1835284020 > 192.168.0.10.2049: 1168
> proc-1886353253
> 01:22:35.046621 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 34077 win
> 43440 <nop,nop,timestamp 17427540 21670901>
> 01:22:35.047209 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 36693 win
> 49232 <nop,nop,timestamp 17427540 21670901>
> 01:22:35.047320 IP 192.168.0.10.2049 > 192.168.0.99.667: . ack 38337 win
> 47784 <nop,nop,timestamp 17427540 21670901>
> 01:22:35.047352 IP 192.168.0.10.2049 > 192.168.0.99.708253668: reply ok 56
> getattr ERROR: unk 10011
> 01:22:35.047375 IP 192.168.0.10.2049 > 192.168.0.99.725030884: reply ok 56
> getattr ERROR: unk 10011
>
> Thomas
> _______________________________________________
> NFSv4 mailing list
> NFSv4 at linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4
More information about the NFSv4
mailing list