NFS Client hangs. Can it be fixed ? - NFS

This is a discussion on NFS Client hangs. Can it be fixed ? - NFS ; Hi All, I am having a problem with the NIC on my laptop. It can't seem to send packets over a certain size. More specifically, 7282 bytes. For example of ping using that size is OK. 7283 bytes and all ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: NFS Client hangs. Can it be fixed ?

  1. NFS Client hangs. Can it be fixed ?

    Hi All,

    I am having a problem with the NIC on my laptop. It can't seem to send
    packets over a certain size. More specifically, 7282 bytes. For example of
    ping using that size is OK. 7283 bytes and all packets are dropped.

    I first noticed the problem due to probs with copying to an NFS share. The
    NFS HOWTO suggested trying the pings with different sizes to see if it is
    a prob of the NIC. That is how I picked up the problem.

    I tried the ping's using windows (using the -l flag I think) and it worked
    fine.

    Any ideas are appreciated.

    Thanks,
    Me

    Ping output.

    ping -s 7282 -c 4 fatcat
    PING fatcat (192.168.0.50) 7282(7310) bytes of data.
    7290 bytes from fatcat (192.168.0.50): icmp_seq=1 ttl=64 time=13.6 ms
    7290 bytes from fatcat (192.168.0.50): icmp_seq=2 ttl=64 time=13.5 ms
    7290 bytes from fatcat (192.168.0.50): icmp_seq=3 ttl=64 time=13.5 ms
    7290 bytes from fatcat (192.168.0.50): icmp_seq=4 ttl=64 time=13.5 ms

    --- fatcat ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3027ms
    rtt min/avg/max/mdev = 13.564/13.588/13.629/0.024 ms

    ping -s 7283 -c 4 fatcat
    PING fatcat (192.168.0.50) 7283(7311) bytes of data.

    --- fatcat ping statistics ---
    4 packets transmitted, 0 received, 100% packet loss, time 3018ms





  2. Re: NFS Client hangs. Can it be fixed ?

    "Noone of Interest" wrote in message news:...
    > Hi All,
    >
    > I am having a problem with the NIC on my laptop. It can't seem to send
    > packets over a certain size. More specifically, 7282 bytes. For example of
    > ping using that size is OK. 7283 bytes and all packets are dropped.
    >
    > I first noticed the problem due to probs with copying to an NFS share. The
    > NFS HOWTO suggested trying the pings with different sizes to see if it is
    > a prob of the NIC. That is how I picked up the problem.
    >
    > I tried the ping's using windows (using the -l flag I think) and it worked
    > fine.


    Most likely, if you switched to using NFS over TCP, the client would size
    TCP segments to the maximum MTU of the route between the client and
    server, and this would just work. Otherwise, you'll want to set rsize
    and wsize to 4096.

    >
    > Any ideas are appreciated.
    >
    > Thanks,
    > Me
    >
    > Ping output.
    >
    > ping -s 7282 -c 4 fatcat
    > PING fatcat (192.168.0.50) 7282(7310) bytes of data.
    > 7290 bytes from fatcat (192.168.0.50): icmp_seq=1 ttl=64 time=13.6 ms
    > 7290 bytes from fatcat (192.168.0.50): icmp_seq=2 ttl=64 time=13.5 ms
    > 7290 bytes from fatcat (192.168.0.50): icmp_seq=3 ttl=64 time=13.5 ms
    > 7290 bytes from fatcat (192.168.0.50): icmp_seq=4 ttl=64 time=13.5 ms
    >
    > --- fatcat ping statistics ---
    > 4 packets transmitted, 4 received, 0% packet loss, time 3027ms
    > rtt min/avg/max/mdev = 13.564/13.588/13.629/0.024 ms
    >
    > ping -s 7283 -c 4 fatcat
    > PING fatcat (192.168.0.50) 7283(7311) bytes of data.
    >
    > --- fatcat ping statistics ---
    > 4 packets transmitted, 0 received, 100% packet loss, time 3018ms


+ Reply to Thread