[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#377024: marked as done (nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT])

Your message dated Mon, 2 Jun 2008 15:07:13 +0200
with message-id <20080602130713.GG29466@stro.at>
and subject line Re: nfs_common: nfs client crash nfs server?
has caused the Debian Bug report #377024,
regarding nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
377024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377024
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: nfs_common
Severity: normal


In the context of a debian etch nfs client, and a debian potato  nfs
server (with low memory),

Since an upgrade from client to kernel 2-6-15, the systems seems to
freeze from time to time. This seems to be  due to nfs not responding.
When nfs replies again, system then works fine again.

On the client side is installed vmware 4.0; it migth interact with
network and kernel.

Moreover at looking packets on the network, it appears that some NFS/TCP
packets seems to have bad checksum (value 0x5a1c).
In a short laps, 12018 / 15510 (77%) TCP packets originated from same machine
have this 0x5a1c bad checksum value (according to ethereal (selection TCP
+ ip source + value 5a1c in checksum field).

two computers are connected via DLink 10/100 Fast ethernet switch.

Here after is a short extract:

      1 No.     Time        Source                Destination
Protocol Info
      2   30876 1328.078832 192.168.236.33        192.168.236.22
TCP      1023 > nfs [ACK] Seq=2510020 Ack=3272024 Win=32767 Len=0
      3
      4 Frame 30876 (54 bytes on wire, 54 bytes captured)
      5 Ethernet II, Src: chypre (00:11:d8:25:30:97), Dst:
192.168.236.22 (00:80:5f:b6:8b:b6)
      6 Internet Protocol, Src: 192.168.236.33 (192.168.236.33), Dst:
192.168.236.22 (192.168.236.22)
      7 Transmission Control Protocol, Src Port: 1023 (1023), Dst Port:
nfs (2049), Seq: 2510020, Ack: 3272024, Len: 0
      8     Source port: 1023 (1023)
      9     Destination port: nfs (2049)
     10     Sequence number: 2510020    (relative sequence number)
     11     Acknowledgement number: 3272024    (relative ack number)
     12     Header length: 20 bytes
     13     Flags: 0x0010 (ACK)
     14     Window size: 32767
     15     Checksum: 0x1d15 [correct]
     16     SEQ/ACK analysis
     17
     18 No.     Time        Source                Destination
Protocol Info
     19   30877 1328.079095 192.168.236.22        192.168.236.33
TCP      nfs > 1023 [PSH, ACK] Seq=3272024 Ack=2510020 Win=32120
Len=1004
     20
     21 Frame 30877 (1058 bytes on wire, 1058 bytes captured)
     22 Ethernet II, Src: 192.168.236.22 (00:80:5f:b6:8b:b6), Dst:
chypre (00:11:d8:25:30:97)
     23 Internet Protocol, Src: 192.168.236.22 (192.168.236.22), Dst:
192.168.236.33 (192.168.236.33)
     24 Transmission Control Protocol, Src Port: nfs (2049), Dst Port:
1023 (1023), Seq: 3272024, Ack: 2510020, Len: 1004
     25     Source port: nfs (2049)
     26     Destination port: 1023 (1023)
     27     Sequence number: 3272024    (relative sequence number)
     28     Next sequence number: 3273028    (relative sequence number)
     29     Acknowledgement number: 2510020    (relative ack number)
     30     Header length: 20 bytes
     31     Flags: 0x0018 (PSH, ACK)
     32     Window size: 32120
     33     Checksum: 0x4975 [correct]
     34     TCP segment data (1004 bytes)
     35 Reassembled TCP Segments (4304 bytes): #30872(380),
#30874(1460), #30875(1460), #30877(1004)
     36 Remote Procedure Call Fragment
     37     Fragment header: 3996 bytes
     38     Fragment Data
     39 Remote Procedure Call Fragment
     40     Fragment header: Last fragment, 300 bytes
     41     Fragment Data
     42
     43 No.     Time        Source                Destination
Protocol Info
     44   30880 1328.118910 192.168.236.33        192.168.236.22
TCP      1023 > nfs [ACK] Seq=2510020 Ack=3273028 Win=32767 Len=0
     45
     46 Frame 30880 (54 bytes on wire, 54 bytes captured)      47
Ethernet II, Src: chypre (00:11:d8:25:30:97), Dst: 192.168.236.22
(00:80:5f:b6:8b:b6)
     48 Internet Protocol, Src: 192.168.236.33 (192.168.236.33), Dst:
192.168.236.22 (192.168.236.22)
     49 Transmission Control Protocol, Src Port: 1023 (1023), Dst Port:
nfs (2049), Seq: 2510020, Ack: 3273028, Len: 0
     50     Source port: 1023 (1023)
     51     Destination port: nfs (2049)
     52     Sequence number: 2510020    (relative sequence number)
     53     Acknowledgement number: 3273028    (relative ack number)
     54     Header length: 20 bytes
     55     Flags: 0x0010 (ACK)
     56     Window size: 32767
     57     Checksum: 0x1929 [correct]
     58     SEQ/ACK analysis
     59
     60 No.     Time        Source                Destination
Protocol Info
     61   30887 1332.000497 192.168.236.33        192.168.236.22
TCP      1023 > nfs [PSH, ACK] Seq=2510020 Ack=3273028 Win=32767 [TCP
CHECKSUM INC        ORRECT] Len=120
     62
     63 Frame 30887 (174 bytes on wire, 174 bytes captured)
     64 Ethernet II, Src: chypre (00:11:d8:25:30:97), Dst:
192.168.236.22 (00:80:5f:b6:8b:b6)
     65 Internet Protocol, Src: 192.168.236.33 (192.168.236.33), Dst:
192.168.236.22 (192.168.236.22)
     66 Transmission Control Protocol, Src Port: 1023 (1023), Dst Port:
nfs (2049), Seq: 2510020, Ack: 3273028, Len: 120
     67     Source port: 1023 (1023)
     68     Destination port: nfs (2049)
     69     Sequence number: 2510020    (relative sequence number)
     70     Next sequence number: 2510140    (relative sequence number)
     71     Acknowledgement number: 3273028    (relative ack number)
     72     Header length: 20 bytes
     73     Flags: 0x0018 (PSH, ACK)
     74     Window size: 32767
     75     Checksum: 0x5a1c [incorrect, should be 0xd02a]
     76 Remote Procedure Call Fragment
     77     Fragment header: Last fragment, 116 bytes
     78     Fragment Data
     79
     80 No.     Time        Source                Destination
Protocol Info
     81   30888 1332.001194 192.168.236.22        192.168.236.33
TCP      nfs > 1023 [PSH, ACK] Seq=3273028 Ack=2510140 Win=32120 Len=100
     82
     83 Frame 30888 (154 bytes on wire, 154 bytes captured)
     84 Ethernet II, Src: 192.168.236.22 (00:80:5f:b6:8b:b6), Dst:
chypre (00:11:d8:25:30:97)
     85 Internet Protocol, Src: 192.168.236.22 (192.168.236.22), Dst:
192.168.236.33 (192.168.236.33)
     86 Transmission Control Protocol, Src Port: nfs (2049), Dst Port:
1023 (1023), Seq: 3273028, Ack: 2510140, Len: 100
     87     Source port: nfs (2049)
     88     Destination port: 1023 (1023)
     89     Sequence number: 3273028    (relative sequence number)
     90     Next sequence number: 3273128    (relative sequence number)
     91     Acknowledgement number: 2510140    (relative ack number)
     92     Header length: 20 bytes
     93     Flags: 0x0018 (PSH, ACK)
     94     Window size: 32120
     95     Checksum: 0x7a95 [correct]
     96     SEQ/ACK analysis
     97 Remote Procedure Call Fragment
     98     Fragment header: Last fragment, 96 bytes
     99     Fragment Data
    100
    101 No.     Time        Source                Destination
Protocol Info
    102   30889 1332.001210 192.168.236.33        192.168.236.22
TCP      1023 > nfs [ACK] Seq=2510140 Ack=3273128 Win=32767 Len=0
    103
    104 Frame 30889 (54 bytes on wire, 54 bytes captured)
    105 Ethernet II, Src: chypre (00:11:d8:25:30:97), Dst:
192.168.236.22 (00:80:5f:b6:8b:b6)
    106 Internet Protocol, Src: 192.168.236.33 (192.168.236.33), Dst:
192.168.236.22 (192.168.236.22)
    107 Transmission Control Protocol, Src Port: 1023 (1023), Dst Port:
nfs (2049), Seq: 2510140, Ack: 3273128, Len: 0
    108     Source port: 1023 (1023)     109     Destination port: nfs
(2049)
    110     Sequence number: 2510140    (relative sequence number)
    111     Acknowledgement number: 3273128    (relative ack number)
    112     Header length: 20 bytes
    113     Flags: 0x0010 (ACK)
    114     Window size: 32767
    115     Checksum: 0x184d [correct]
    116     SEQ/ACK analysis
    117
    118 No.     Time        Source                Destination
Protocol Info
    119   30890 1332.001286 192.168.236.33        192.168.236.22
TCP      1023 > nfs [PSH, ACK] Seq=2510140 Ack=3273128 Win=32767 [TCP
CHECKSUM INC        ORRECT] Len=120
    120
    121 Frame 30890 (174 bytes on wire, 174 bytes captured)
    122 Ethernet II, Src: chypre (00:11:d8:25:30:97), Dst:
192.168.236.22 (00:80:5f:b6:8b:b6)
    123 Internet Protocol, Src: 192.168.236.33 (192.168.236.33), Dst:
192.168.236.22 (192.168.236.22)
    124 Transmission Control Protocol, Src Port: 1023 (1023), Dst Port:
nfs (2049), Seq: 2510140, Ack: 3273128, Len: 120
    125     Source port: 1023 (1023)
    126     Destination port: nfs (2049)
    127     Sequence number: 2510140    (relative sequence number)
    128     Next sequence number: 2510260    (relative sequence number)
    129     Acknowledgement number: 3273128    (relative ack number)
    130     Header length: 20 bytes
    131     Flags: 0x0018 (PSH, ACK)
    132     Window size: 32767
    133     Checksum: 0x5a1c [incorrect, should be 0xc93e]
    134 Remote Procedure Call Fragment
    135     Fragment header: Last fragment, 116 bytes
    136     Fragment Data



Why are there Checksum: 0x5a1c [incorrect, ?


Regards.



-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)

--- End Message ---
--- Begin Message --- 
Version: 2.6.18-1

> Since an upgrade from client to kernel 2-6-15

closing as ancient version, thanks for feedback.

-- 
maks

--- End Message ---
Reply to: