This is a discussion on nfs error 1308 (tcpdump) - NFS ; Hello, can anybody tell me what those errors mean or where to read about it? 22:41:05.698055 IP (tos 0x0, ttl 60, id 40013, offset 0, flags [DF], length: 1348) 10.248.218.37.2049 > 10.184.86.15.1126236148: reply ERR 1308 22:41:05.699819 IP (tos 0x0, ttl ...
Hello,
can anybody tell me what those errors mean or where to read about it?
22:41:05.698055 IP (tos 0x0, ttl 60, id 40013, offset 0, flags [DF],
length: 1348) 10.248.218.37.2049 > 10.184.86.15.1126236148: reply ERR 1308
22:41:05.699819 IP (tos 0x0, ttl 57, id 47508, offset 0, flags [DF],
length: 164) 10.184.86.15.2014440224 > 10.248.218.37.2049: 124 read [|nfs]
22:41:05.699887 IP (tos 0x0, ttl 60, id 40015, offset 0, flags [DF],
length: 2960) 10.248.218.37.2049 > 10.184.86.15.2014440224: reply ok
2920 read [|nfs]
22:41:05.701816 IP (tos 0x0, ttl 57, id 47509, offset 0, flags [DF],
length: 40) 10.184.86.15.32768 > 10.248.218.37.2049: . [tcp sum ok]
124:124(0) ack 4229 win 65535
22:41:05.701828 IP (tos 0x0, ttl 60, id 40020, offset 0, flags [DF],
length: 1348) 10.248.218.37.2049 > 10.184.86.15.536877268: reply ERR 1308
Thank you and regards,
Holger
Holger van Koll wrote:
> Hello,
>
> can anybody tell me what those errors mean or where to read about it?
Using tcpdump to analyze NFS problems is not an effective use of your
time.
Use tethereal to create a capture file and then use ethereal to
analyze the problem.
