Mailinglist Archive: opensuse (686 mails)

< Previous Next >
Re: [opensuse] Problem mounting nfs partition on 12.3
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Sun, 14 Jul 2013 22:11:58 +0200 (CEST)
  • Message-id: <alpine.LNX.2.00.1307142128430.16893@Telcontar.valinor>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-ID: <alpine.LNX.2.00.1307142139130.16893@Telcontar.valinor>


On Sunday, 2013-07-14 at 22:51 +0400, Andrey Borzenkov wrote:
В Sun, 14 Jul 2013 17:29:21 +0200 (CEST) "Carlos E. R." <> пишет:


You see, the same server is working with versions 4 and 3, simultaneously.

Ehh ... minas-tirith mounts also using UDP and not TCP, which confirms
that there is some connectivity issue.


A packet capture, edited to reduce size:

No. Time Source Destination Protocol
Length Info
249 15:35:33.385373000 192.168.1.129 192.168.1.14 TCP
74 telnets > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1
TSval=26851809 TSecr=0 WS=64
Transmission Control Protocol, Src Port: telnets (992), Dst Port: nfs (2049),
Seq: 0, Len: 0

No. Time Source Destination Protocol
Length Info
250 15:35:33.385445000 192.168.1.14 192.168.1.129 TCP
74 nfs > telnets [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460
SACK_PERM=1 TSval=647243754 TSecr=26851809 WS=128
279 15:35:34.586491000 192.168.1.14 192.168.1.129 TCP
74 [TCP Retransmission] nfs > telnets [SYN, ACK] Seq=0 Ack=1 Win=14480
Len=0 MSS=1460 SACK_PERM=1 TSval=647244956 TSecr=26851809 WS=128

So SYN request comes to NFS server and NFS server answers to this. But
your client apparently ignores it. So issues are with your client, not
your server.

The laptop does not receive that package. Iptraf showed it was not received, and I'm running wireshark on both computers and I do not see the response.


Retransmission? From both sides?


Yes. Which part surprises you?

Both. It has to be the router in the midle, it has changed recently. But it is very strange: pings gets trhough, I'm connected to the laptop via "ssh -Y", running wireshark over that ssh connection, thunderbird is connected via imap on the server... no problems, it works. Why not nfs? All those use tcp.




A sucesful connection (version 3) goes like this:

No. Time Source Destination Protocol
Length Info
90 15:59:58.752892000 192.168.1.129 192.168.1.14 TCP
74 57233 > sunrpc [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1
TSval=28317123 TSecr=
91 15:59:58.752967000 192.168.1.14 192.168.1.129 TCP
74 sunrpc > 57233 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460
SACK_PERM=1 TSval=6487
98 15:59:59.133783000 192.168.1.129 192.168.1.14 ICMP
98 Echo (ping) request id=0x2636, seq=2424/30729, ttl=64
99 15:59:59.133811000 192.168.1.14 192.168.1.129 ICMP
98 Echo (ping) reply id=0x2636, seq=2424/30729, ttl=64
116 15:59:59.754500000 192.168.1.14 192.168.1.129 TCP
74 [TCP Retransmission] sunrpc > 57233 [SYN, ACK] Seq=0 Ack=1 Win=14480
Len=0 MSS=1460 S
160 16:00:01.754498000 192.168.1.14 192.168.1.129 TCP
74 [TCP Retransmission] sunrpc > 57233 [SYN, ACK] Seq=0 Ack=1 Win=14480
Len=0 MSS=1460 S
161 16:00:01.757790000 192.168.1.129 192.168.1.14 TCP
74 [TCP Retransmission] 57233 > sunrpc [SYN] Seq=0 Win=14600 Len=0 MSS=1460
SACK_PERM=1
162 16:00:01.757808000 192.168.1.14 192.168.1.129 TCP
74 [TCP Retransmission] sunrpc > 57233 [SYN, ACK] Seq=0 Ack=1 Win=14480
Len=0 MSS=1460 S
173 16:00:02.341905000 192.168.1.14 192.168.1.129 ICMP
98 Echo (ping) request id=0x70f4, seq=8814/28194, ttl=64
174 16:00:02.343809000 192.168.1.129 192.168.1.14 ICMP
98 Echo (ping) reply id=0x70f4, seq=8814/28194, ttl=64
259 16:00:05.754505000 192.168.1.14 192.168.1.129 TCP
74 [TCP Retransmission] sunrpc > 57233 [SYN, ACK] Seq=0 Ack=1 Win=14480
Len=0 MSS=1460 S
302 16:00:07.774018000 192.168.1.129 192.168.1.14 TCP
74 [TCP Retransmission] 57233 > sunrpc [SYN] Seq=0 Win=14600 Len=0 MSS=1460
SACK_PERM=1
303 16:00:07.774053000 192.168.1.14 192.168.1.129 TCP
74 [TCP Retransmission] sunrpc > 57233 [SYN, ACK] Seq=0 Ack=1 Win=14480
Len=0 MSS=1460 S

You get *EXACTLY* the same problem. Client never replies to SYN ACK
from server so connection is never established.

329 16:00:08.763987000 192.168.1.129 192.168.1.14 Portmap
98 V2 GETPORT Call (Reply In 332) NFS(100003) V:3 UDP

And client falls back to UDP. Which of course cannot work with NFS V4
which dropped support for UDP entirely.

So from information you provided it is either client or network issue.
If trace was captured on client, it is most likely client. For a start
check firewall on client ...

I tried also with firewal down on both sides, no difference.


I restarted the test that was running with ipraf with both firewalls down. I see no difference, but I have to wait the 3 minutes timeout.


If the router is capturing those packages, it must be because it thinks they are for him, because it has fileserver capabilities (which I do not use). But it makes no sense, the IP destination are not for it!

Ok, capture on laptop:

No. Time Source Destination Protocol
Length Info
563 15.005465000 192.168.1.129 192.168.1.14 TCP 74
870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1 TSval=36864829
TSecr=0 WS=64
606 18.015577000 192.168.1.129 192.168.1.14 TCP 74
[TCP Retransmission] 870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1
TSval=36867840 TSecr=0 WS=64
688 24.031598000 192.168.1.129 192.168.1.14 TCP 74
[TCP Retransmission] 870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1
TSval=36873856 TSecr=0 WS=64
917 36.063562000 192.168.1.129 192.168.1.14 TCP 74
[TCP Retransmission] 870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1
TSval=36885888 TSecr=0 WS=64
1321 60.127563000 192.168.1.129 192.168.1.14 TCP 74
[TCP Retransmission] 870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1
TSval=36909952 TSecr=0 WS=64
3704 108.255585000 192.168.1.129 192.168.1.14 TCP 74
[TCP Retransmission] 870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1
TSval=36958080 TSecr=0 WS=64

And on the server:

No. Time Source Destination Protocol
Length Info
580 21:47:15.918490000 192.168.1.129 192.168.1.14 TCP 74
870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1 TSval=36864829
TSecr=0 WS=64
582 21:47:15.918508000 192.168.1.14 192.168.1.129 TCP 74
nfs > 870 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1
TSval=669546288 TSecr=36864829 WS=128
642 21:47:17.120493000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0
MSS=1460 SACK_PERM=1 TSval=669547490 TSecr=36864829 WS=128
690 21:47:18.928453000 192.168.1.129 192.168.1.14 TCP 74
[TCP Retransmission] 870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460
SACK_PERM=1 TSval=36867840 TSecr=0 WS=64
691 21:47:18.928477000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0
MSS=1460 SACK_PERM=1 TSval=669549297 TSecr=36864829 WS=128
704 21:47:19.320497000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0
MSS=1460 SACK_PERM=1 TSval=669549690 TSecr=36864829 WS=128
816 21:47:23.320494000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0
MSS=1460 SACK_PERM=1 TSval=669553690 TSecr=36864829 WS=128
904 21:47:24.944675000 192.168.1.129 192.168.1.14 TCP 74
[TCP Retransmission] 870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460
SACK_PERM=1 TSval=36873856 TSecr=0 WS=64
905 21:47:24.944691000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0
MSS=1460 SACK_PERM=1 TSval=669555314 TSecr=36864829 WS=128
1171 21:47:31.520497000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0
MSS=1460 SACK_PERM=1 TSval=669561890 TSecr=36864829 WS=128
1368 21:47:36.977082000 192.168.1.129 192.168.1.14 TCP 74
[TCP Retransmission] 870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460
SACK_PERM=1 TSval=36885888 TSecr=0 WS=64
1369 21:47:36.977120000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0
MSS=1460 SACK_PERM=1 TSval=669567346 TSecr=36864829 WS=128
1823 21:47:47.920502000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0
MSS=1460 SACK_PERM=1 TSval=669578290 TSecr=36864829 WS=128
2262 21:48:01.041897000 192.168.1.129 192.168.1.14 TCP 74
[TCP Retransmission] 870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460
SACK_PERM=1 TSval=36909952 TSecr=0 WS=64
2263 21:48:01.041918000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0
MSS=1460 SACK_PERM=1 TSval=669591411 TSecr=36864829 WS=128
5861 21:48:49.171584000 192.168.1.129 192.168.1.14 TCP 74
[TCP Retransmission] 870 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460
SACK_PERM=1 TSval=36958080 TSecr=0 WS=64
5862 21:48:49.171609000 192.168.1.14 192.168.1.129 TCP 74
[TCP Previous segment not captured] nfs > 870 [SYN, ACK] Seq=1457079676
Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1 TSval=669639541 TSecr=36958080 WS=128
6225 21:48:50.574490000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=1457079676 Ack=1 Win=14480
Len=0 MSS=1460 SACK_PERM=1 TSval=669640944 TSecr=36958080 WS=128
6527 21:48:52.574490000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=1457079676 Ack=1 Win=14480
Len=0 MSS=1460 SACK_PERM=1 TSval=669642944 TSecr=36958080 WS=128
7470 21:48:56.574493000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=1457079676 Ack=1 Win=14480
Len=0 MSS=1460 SACK_PERM=1 TSval=669646944 TSecr=36958080 WS=128
8263 21:49:04.774494000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=1457079676 Ack=1 Win=14480
Len=0 MSS=1460 SACK_PERM=1 TSval=669655144 TSecr=36958080 WS=128
9049 21:49:20.774494000 192.168.1.14 192.168.1.129 TCP 74
[TCP Retransmission] nfs > 870 [SYN, ACK] Seq=1457079676 Ack=1 Win=14480
Len=0 MSS=1460 SACK_PERM=1 TSval=669671144 TSecr=36958080 WS=128

See? The laptop, with both firewalls down, does not see those packages. And
I'm working all the time remotely from the deskop on the laptop, no network
problems detected. I have pings running all the time from both sides, no
losses.

Those packages are removed intentionally by something.

Quick test. The router has no disk plugged in, so it should be disabled. It does not support nfs. I disable "storage sharing" (samba). I disable FTP and media server. And print server. All off.

Try nfs connect from the laptop... failure.


Ok, so the nfs tcp packages from the laptop fails. If it was a generalized failure, nfs udp packages would be lost, too, and I have sendt and received many megabytes over it yesterday, over nfs 3. Or tcp packages from other services. It makes no sense :-/

- -- Cheers,
Carlos E. R.
(from 12.3 x86_64 "Dartmouth" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAlHjBhYACgkQtTMYHG2NR9U8WgCgicG08CcU8Tn8g7IT495SIhQC
doUAoIPcvY2XP5a3GOP7rruZb8Ifz9x3
=ZA3M
-----END PGP SIGNATURE-----
< Previous Next >
Follow Ups