nfsmnthelp holding up server nfsd? - Aix

This is a discussion on nfsmnthelp holding up server nfsd? - Aix ; HI, We have a lot of machines that nfs mount f/s from an aix 53-05 nfs server. We are not using NFS4. All client machines are at 51-04 A handfull of the client machines cause us a problem. Trying to ...

+ Reply to Thread
Results 1 to 17 of 17

Thread: nfsmnthelp holding up server nfsd?

  1. nfsmnthelp holding up server nfsd?

    HI,

    We have a lot of machines that nfs mount f/s from an aix 53-05 nfs
    server. We are not using NFS4.

    All client machines are at 51-04

    A handfull of the client machines cause us a problem. Trying to issue
    a mount command from those machines appears to hang, leaving an
    nfsmnthelp process running.

    The trouble is, it prevents any other client mounting a f/s from the
    server. They all time out.

    There is no network congestion. tcpdump on the server shows a very
    low level of nfs activity. spray drops 0 packets. tcp/ip is not
    dropping packets. nfsstat show an increasingly high number of
    BADCALLS, although specifically what that indicates I am not sure of.

    Killing the 'rogue' nfsmnthelp on the client frees everything up
    again, other clients can mount from the server, mounts that have been
    attempted and are hung suddenly complete.

    Anyone have any ideas?

    Thanks,

    Matt.


  2. Re: nfsmnthelp holding up server nfsd?

    On 5 Jul, 12:03, MattWarren wrote:
    > HI,
    >
    > We have a lot of machines that nfs mount f/s from an aix 53-05 nfs
    > server. We are not using NFS4.
    >
    > All client machines are at 51-04
    >
    > A handfull of the client machines cause us a problem. Trying to issue
    > a mount command from those machines appears to hang, leaving an
    > nfsmnthelp process running.
    >
    > The trouble is, it prevents any other client mounting a f/s from the
    > server. They all time out.
    >
    > There is no network congestion. tcpdump on the server shows a very
    > low level of nfs activity. spray drops 0 packets. tcp/ip is not
    > dropping packets. nfsstat show an increasingly high number of
    > BADCALLS, although specifically what that indicates I am not sure of.
    >
    > Killing the 'rogue' nfsmnthelp on the client frees everything up
    > again, other clients can mount from the server, mounts that have been
    > attempted and are hung suddenly complete.
    >
    > Anyone have any ideas?
    >
    > Thanks,
    >
    > Matt.


    Further investigation.

    The client sits there trying to perform it's hardmount displaying

    NFS server twinkletoes not responding still trying

    while a tcpdump on the server;
    tcpdump -vvv -A -N -ttt -s1024 -u -X -ien0 | grep nfs

    show periodically large numbers of fsinfo and other nfs requests
    coming from the client. The server however, just never replies.

    An Identical client (The opposite machine in the cluster - and it
    really is identical, for once ;P ) mounts the filesystems no problem.


  3. Re: nfsmnthelp holding up server nfsd?

    What are the option for
    nfsd
    rpc.mountd

    Not that you use the -c option for the nfsd or -N for the rpc.mountd

    On the client as well as on the server itself issue a

    $ showmount -e NFSSERVER

    and see what happens.

    hth
    Hajo


  4. Re: nfsmnthelp holding up server nfsd?

    On 5 Jul, 17:07, Hajo Ehlers wrote:
    > What are the option for
    > nfsd
    > rpc.mountd
    >
    > Not that you use the -c option for the nfsd or -N for the rpc.mountd
    >
    > On the client as well as on the server itself issue a
    >
    > $ showmount -e NFSSERVER
    >
    > and see what happens.
    >
    > hth
    > Hajo


    Hi,

    RPC etc.. all seems to be fine and reporting as it should;

    from client
    root@jinglebells:/apps/sys/bin> showmount -e twinkletoes
    export list for twinkletoes:
    /tmp/invscout (everyone)
    /data/nim/software (everyone)
    /data/nim/spot/spot_aix530/spot_aix530/usr 10.0.45.8
    /data/nim/mksysb (everyone)
    root@jinglebells:/apps/sys/bin>

    from server
    twinkletoes:/etc> showmount -e twinkletoes
    export list for twinkletoes:
    /tmp/invscout (everyone)
    /data/nim/software (everyone)
    /data/nim/spot/spot_aix530/spot_aix530/usr 10.0.45.8
    /data/nim/mksysb (everyone)


    Currently I'm trying to determine exactly what can cause the BADCALLS
    number to rise in nfsstat -s because every failed attempt from this
    client to mount a filesystem increments BADCALLS a bunch. Hopefully
    understanding exactly what a badcall is will give further clues...



  5. Re: nfsmnthelp holding up server nfsd?

    On 5 Jul, 17:22, MattWarren wrote:
    > On 5 Jul, 17:07, Hajo Ehlers wrote:
    >
    > > What are the option for
    > > nfsd
    > > rpc.mountd

    >
    > > Not that you use the -c option for the nfsd or -N for the rpc.mountd

    >
    > > On the client as well as on the server itself issue a

    >
    > > $ showmount -e NFSSERVER

    >
    > > and see what happens.

    >
    > > hth
    > > Hajo

    >
    > Hi,
    >
    > RPC etc.. all seems to be fine and reporting as it should;
    >
    > from client
    > root@jinglebells:/apps/sys/bin> showmount -e twinkletoes
    > export list for twinkletoes:
    > /tmp/invscout (everyone)
    > /data/nim/software (everyone)
    > /data/nim/spot/spot_aix530/spot_aix530/usr 10.0.45.8
    > /data/nim/mksysb (everyone)
    > root@jinglebells:/apps/sys/bin>
    >
    > from server
    > twinkletoes:/etc> showmount -e twinkletoes
    > export list for twinkletoes:
    > /tmp/invscout (everyone)
    > /data/nim/software (everyone)
    > /data/nim/spot/spot_aix530/spot_aix530/usr 10.0.45.8
    > /data/nim/mksysb (everyone)
    >
    > Currently I'm trying to determine exactly what can cause the BADCALLS
    > number to rise in nfsstat -s because every failed attempt from this
    > client to mount a filesystem increments BADCALLS a bunch. Hopefully
    > understanding exactly what a badcall is will give further clues...


    More detail;

    mounting the filesystem to a different client, and using tcpdump on
    the server to watch nfs request, only 1 or two nfs requests come
    through, and the mount compeltes almost instantaneously.

    mounting from the problem client and watching tcpdump, the client
    sends hundreds and hundreds of fsinfo requests immediatley. I see the
    server reply to a few with
    reply ok 168 fsinfo
    but then appears to give up and doesnt respond anymore.


  6. Re: nfsmnthelp holding up server nfsd?

    On 5 Jul, 17:40, MattWarren wrote:
    > On 5 Jul, 17:22, MattWarren wrote:
    >
    >
    >
    >
    >
    > > On 5 Jul, 17:07, Hajo Ehlers wrote:

    >
    > > > What are the option for
    > > > nfsd
    > > > rpc.mountd

    >
    > > > Not that you use the -c option for the nfsd or -N for the rpc.mountd

    >
    > > > On the client as well as on the server itself issue a

    >
    > > > $ showmount -e NFSSERVER

    >
    > > > and see what happens.

    >
    > > > hth
    > > > Hajo

    >
    > > Hi,

    >
    > > RPC etc.. all seems to be fine and reporting as it should;

    >
    > > from client
    > > root@jinglebells:/apps/sys/bin> showmount -e twinkletoes
    > > export list for twinkletoes:
    > > /tmp/invscout (everyone)
    > > /data/nim/software (everyone)
    > > /data/nim/spot/spot_aix530/spot_aix530/usr 10.0.45.8
    > > /data/nim/mksysb (everyone)
    > > root@jinglebells:/apps/sys/bin>

    >
    > > from server
    > > twinkletoes:/etc> showmount -e twinkletoes
    > > export list for twinkletoes:
    > > /tmp/invscout (everyone)
    > > /data/nim/software (everyone)
    > > /data/nim/spot/spot_aix530/spot_aix530/usr 10.0.45.8
    > > /data/nim/mksysb (everyone)

    >
    > > Currently I'm trying to determine exactly what can cause the BADCALLS
    > > number to rise in nfsstat -s because every failed attempt from this
    > > client to mount a filesystem increments BADCALLS a bunch. Hopefully
    > > understanding exactly what a badcall is will give further clues...

    >
    > More detail;
    >
    > mounting the filesystem to a different client, and using tcpdump on
    > the server to watch nfs request, only 1 or two nfs requests come
    > through, and the mount compeltes almost instantaneously.
    >
    > mounting from the problem client and watching tcpdump, the client
    > sends hundreds and hundreds of fsinfo requests immediatley. I see the
    > server reply to a few with
    > reply ok 168 fsinfo
    > but then appears to give up and doesnt respond anymore.- Hide quoted text -
    >
    > - Show quoted text -


    Even more;

    Here are the tcpdumps for the first few moments from the propblem
    client and the server.

    client
    17:47:06.129163014 loncmxs1024.4693d89f >
    loncmxs1018.uk.net.intra.nfs: 44 proc-18976 (DF)
    17:47:06.129726434 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.4693d89f: reply ok 28 (DF)
    17:47:06.133629978 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-2048 (DF)
    17:47:06.133653644 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-2048 (DF)
    17:47:06.133671099 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-2048 (DF)
    17:47:06.133687938 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-152 (DF)
    17:47:06.133704226 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.133952162 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.133968835 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.133985339 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.134001866 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-45390 (DF)
    17:47:06.134019045 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-21144 (DF)
    17:47:06.134039054 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-36252 (DF)
    17:47:06.134057038 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-17520 (DF)
    17:47:06.134073260 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-65065 (DF)
    17:47:06.134090285 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16529 (DF)
    17:47:06.134107737 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.134126996 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-20052 (DF)
    17:47:06.134134004 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.134145516 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-257 (DF)
    17:47:06.134175669 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-163 (DF)
    17:47:06.134192153 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-127 (DF)
    17:47:06.134208215 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-60 (DF)
    17:47:06.134228141 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-113 (DF)
    17:47:06.134244765 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-162 (DF)
    17:47:06.134262441 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-171 (DF)
    17:47:06.134279955 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-48 (DF)
    17:47:06.134296461 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-1993 (DF)
    17:47:06.134317565 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-5000 (DF)
    17:47:06.134333976 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.134350503 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-60 (DF)
    17:47:06.134366557 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-40 (DF)
    17:47:06.134374834 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.134385143 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.134413152 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-71 (DF)
    17:47:06.134429344 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-18649 (DF)
    17:47:06.134446520 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-44073 (DF)
    17:47:06.134463644 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-2048 (DF)
    17:47:06.134549972 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-33678 (DF)
    17:47:06.134567661 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.134581880 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.134596351 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.134610836 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.134625220 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-18766 (DF)
    17:47:06.134642289 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.134656944 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-21589 (DF)
    17:47:06.134671190 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-60 (DF)
    17:47:06.148970200 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149020542 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149072888 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149129342 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149142099 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149145165 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149172695 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149186432 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149219607 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149229926 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149268625 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149319036 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-60 (DF)
    17:47:06.149320848 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149339054 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149368940 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149408330 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.149430589 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.149451510 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 setattr [|nfs] (DF)
    17:47:06.149473343 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.149498262 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-8330 (DF)
    17:47:06.149519284 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-35650 (DF)
    17:47:06.149539498 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-2475 (DF)
    17:47:06.149559794 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-8590 (DF)
    17:47:06.149708282 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149770032 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149791604 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-19130 (DF)
    17:47:06.149811531 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149826066 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-18649 (DF)
    17:47:06.149851333 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-8539 (DF)
    17:47:06.149861996 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149873884 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.149897830 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-8330 (DF)
    17:47:06.149914562 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149920104 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-2372 (DF)
    17:47:06.149935307 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149951704 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-2370 (DF)
    17:47:06.149965840 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.149977075 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-2368 (DF)
    17:47:06.150000842 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-8612 (DF)
    17:47:06.150013537 loncmxs1018.uk.net.intra.nfs >
    loncmxs1024.682fc99a: reply ok 168 (DF)
    17:47:06.205961258 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.205980963 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.206000948 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.206020462 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-45390 (DF)
    17:47:06.206043059 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-21144 (DF)
    17:47:06.206113702 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206132435 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206150045 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206176365 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206197938 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206215912 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206233495 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206251262 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206269037 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206290112 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206307988 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206325728 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206343492 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206362150 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206383778 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206402545 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206421341 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206440047 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206459064 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206481283 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206500142 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206518819 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206538067 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206557467 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206579835 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206599386 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.206621092 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-9649 (DF)
    17:47:06.206711050 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-9789 (DF)
    17:47:06.206731322 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-9929 (DF)
    17:47:06.206754504 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-10069 (DF)
    17:47:06.206774883 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-10209 (DF)
    17:47:06.206795043 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-10349 (DF)
    17:47:06.206814571 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-10489 (DF)
    17:47:06.206834944 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-35927 (DF)
    17:47:06.206863365 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.206884672 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.206904848 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-8329 (DF)
    17:47:06.206925028 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-8329 (DF)
    17:47:06.206944542 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-8329 (DF)
    17:47:06.206969000 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207042684 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207061741 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207081505 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207100370 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207168131 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207185725 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207203385 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207221258 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207239017 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207260082 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207278016 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207295490 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207313236 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207331045 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207352155 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207370046 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207387787 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207405950 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207424179 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207445512 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207463601 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207481631 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207499895 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207517960 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207539437 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207557996 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207577468 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207596591 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207615541 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207638898 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207658075 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207677179 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207696587 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.207715497 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-3696 (DF)
    17:47:06.207742078 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.207762936 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.207782548 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.207801222 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-45390 (DF)
    17:47:06.207820223 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-21144 (DF)
    17:47:06.207842239 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.207860953 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.207879690 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.207898359 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.207917152 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.207939499 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.207960649 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.207980397 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208000204 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208020287 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208043737 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208063940 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208083066 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208102527 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208121751 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208144425 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208163530 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208182799 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208201989 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208221700 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208244653 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208264539 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208285391 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.208359086 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.208379432 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.208403460 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.208423929 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208444387 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208487328 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208511967 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208539969 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208565334 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208586779 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208607200 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208628044 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-29299 (DF)
    17:47:06.208656372 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.208677419 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.208697752 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-8329 (DF)
    17:47:06.208718101 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-8329 (DF)
    17:47:06.208738075 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-8329 (DF)
    17:47:06.208761507 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.208784051 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.208859054 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.208879151 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.208898979 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.208922554 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.208942855 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.208962915 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.208982825 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209001946 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209024862 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209044583 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209064797 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209084976 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209104798 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209127305 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209147606 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209167373 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209187334 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209207061 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209230546 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209250733 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209272516 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209407055 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209429546 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209454109 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209474663 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209494940 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209515358 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209535548 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209559259 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209579699 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209600628 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.209728519 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.209748618 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.209771433 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.209790048 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-45390 (DF)
    17:47:06.209808621 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-21144 (DF)
    17:47:06.209827156 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.209845649 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.209867405 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.209885880 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.209904971 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.209923639 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.209995049 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.210018944 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.210454340 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-54229 (DF)
    17:47:06.210474383 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-54369 (DF)
    17:47:06.210493291 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-54509 (DF)
    17:47:06.210512795 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-54649 (DF)
    17:47:06.210536572 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-54789 (DF)
    17:47:06.210555799 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-54929 (DF)
    17:47:06.210574973 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-55069 (DF)
    17:47:06.210720963 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.210740211 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.210762949 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.210781455 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.210799892 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.210818914 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-55909 (DF)
    17:47:06.210892718 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.210965348 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.210984597 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.211074643 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.211093599 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.211113658 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.211136949 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.211156245 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.211174940 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.211192930 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.211217162 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.211241323 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211323031 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211340721 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211358168 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211375736 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211397133 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211414854 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211433286 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211504720 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211521606 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211541833 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211559137 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211576074 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.211594777 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-59969 (DF)
    17:47:06.211669304 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-60109 (DF)
    17:47:06.211689600 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-60249 (DF)
    17:47:06.211706489 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-60389 (DF)
    17:47:06.211723205 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-60529 (DF)
    17:47:06.211787335 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.212150149 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212172639 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212229886 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212299562 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212314914 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212330372 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212392305 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212407811 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212423437 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212438709 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212453992 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212472774 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212487480 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212502932 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212517712 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.212537365 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.212556001 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.212570965 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.212586104 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-45390 (DF)
    17:47:06.212601054 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-21144 (DF)
    17:47:06.212616171 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.212634361 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.212649367 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.212664338 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.212679897 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.212694845 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.212766429 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.212787671 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.212808951 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 read [|nfs] (DF)
    17:47:06.212829218 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.212849447 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.212870211 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.212886172 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.212902277 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.212918269 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.212933499 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.212999136 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.213018399 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.213099652 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.213115905 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.213131802 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.213151277 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.213167798 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.213183656 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-1153 (DF)
    17:47:06.213677716 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.213697595 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-1433 (DF)
    17:47:06.213717721 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-1573 (DF)
    17:47:06.213732671 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-1713 (DF)
    17:47:06.213747600 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-1853 (DF)
    17:47:06.213762975 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-1993 (DF)
    17:47:06.213778545 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-2133 (DF)
    17:47:06.213797158 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-2273 (DF)
    17:47:06.213812110 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-2413 (DF)
    17:47:06.213826696 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.213846452 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.213863400 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.213881472 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.213896758 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.213911857 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.213926586 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.213941938 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.213960279 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.213975423 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 read [|nfs] (DF)
    17:47:06.213990352 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.214005689 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.215182496 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215206359 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215222282 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215238469 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 read [|nfs] (DF)
    17:47:06.215254129 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.215268731 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.215326569 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.215342622 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.215358096 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.215373044 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.215388462 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-5213 (DF)
    17:47:06.215406591 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-32835 (DF)
    17:47:06.215421599 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.215437475 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.215453398 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.215548908 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215568047 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215583407 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215599011 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215614294 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215629760 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215648428 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215663825 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215679392 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215761595 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215777104 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215795751 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215854798 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215869560 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-3696 (DF)
    17:47:06.215883901 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 null (DF)
    17:47:06.215897824 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 writecache [|nfs] (DF)
    17:47:06.215914868 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-16384 (DF)
    17:47:06.215929097 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-45390 (DF)
    17:47:06.215990403 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.216059201 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.216074614 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.216096250 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.216111461 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.216127017 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)
    17:47:06.216142627 loncmxs1024.682fc99a >
    loncmxs1018.uk.net.intra.nfs: 140 proc-51610 (DF)


    Server
    000095 IP (tos 0x0, ttl 57, id 29456, offset 0, flags [DF], length:
    84) loncmxs1024.1184094367 > loncmxs1018.nfs: 44 null
    000042 IP (tos 0x0, ttl 57, id 29463, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000065 IP (tos 0x0, ttl 57, id 29464, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 57, id 29465, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000026 IP (tos 0x0, ttl 57, id 29466, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24132, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000022 IP (tos 0x0, ttl 57, id 29467, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000152 IP (tos 0x0, ttl 60, id 24133, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000030 IP (tos 0x0, ttl 57, id 29469, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29470, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000037 IP (tos 0x0, ttl 57, id 29471, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29472, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29473, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000028 IP (tos 0x0, ttl 57, id 29474, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29475, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000030 IP (tos 0x0, ttl 57, id 29476, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29477, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29478, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000044 IP (tos 0x0, ttl 57, id 29479, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000009 IP (tos 0x0, ttl 57, id 29480, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000005 IP (tos 0x0, ttl 57, id 29481, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29482, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000008 IP (tos 0x0, ttl 57, id 29483, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000029 IP (tos 0x0, ttl 57, id 29484, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000022 IP (tos 0x0, ttl 57, id 29485, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29486, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000034 IP (tos 0x0, ttl 57, id 29487, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29488, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29489, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000005 IP (tos 0x0, ttl 57, id 29490, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29491, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000008 IP (tos 0x0, ttl 57, id 29492, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000007 IP (tos 0x0, ttl 57, id 29493, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000009 IP (tos 0x0, ttl 57, id 29494, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000039 IP (tos 0x0, ttl 57, id 29495, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29496, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000007 IP (tos 0x0, ttl 57, id 29497, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000041 IP (tos 0x0, ttl 60, id 24135, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000041 IP (tos 0x0, ttl 57, id 29498, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 60, id 24136, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000035 IP (tos 0x0, ttl 57, id 29499, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000029 IP (tos 0x0, ttl 60, id 24137, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000005 IP (tos 0x0, ttl 57, id 29500, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29501, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000005 IP (tos 0x0, ttl 57, id 29502, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000007 IP (tos 0x0, ttl 57, id 29503, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000006 IP (tos 0x0, ttl 60, id 24139, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29504, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000008 IP (tos 0x0, ttl 57, id 29505, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24140, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000030 IP (tos 0x0, ttl 60, id 24141, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 60, id 24142, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000027 IP (tos 0x0, ttl 60, id 24143, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000002 IP (tos 0x0, ttl 57, id 29506, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29507, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 60, id 24144, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 60, id 24145, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29508, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 60, id 24146, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000024 IP (tos 0x0, ttl 60, id 24147, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29509, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 60, id 24148, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 60, id 24149, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 60, id 24150, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000020 IP (tos 0x0, ttl 60, id 24151, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000036 IP (tos 0x0, ttl 60, id 24152, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000035 IP (tos 0x0, ttl 57, id 29510, offset 0, flags [DF], length:
    880) loncmxs1024.1747962266 > loncmxs1018.nfs: 840 fsinfo [|nfs]
    000022 IP (tos 0x0, ttl 57, id 29511, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29512, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000008 IP (tos 0x0, ttl 57, id 29513, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000009 IP (tos 0x0, ttl 57, id 29514, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 57, id 29515, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000033 IP (tos 0x0, ttl 60, id 24153, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29516, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000036 IP (tos 0x0, ttl 60, id 24154, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 60, id 24155, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29517, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24156, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000036 IP (tos 0x0, ttl 57, id 29518, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 60, id 24157, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000021 IP (tos 0x0, ttl 57, id 29519, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29520, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24158, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000032 IP (tos 0x0, ttl 60, id 24159, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000035 IP (tos 0x0, ttl 60, id 24160, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000034 IP (tos 0x0, ttl 60, id 24161, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000048 IP (tos 0x0, ttl 60, id 24162, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24163, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29521, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 60, id 24164, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24165, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000035 IP (tos 0x0, ttl 60, id 24166, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000042 IP (tos 0x0, ttl 60, id 24167, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000096 IP (tos 0x0, ttl 57, id 29522, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000003 IP (tos 0x0, ttl 60, id 24168, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 60, id 24169, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000033 IP (tos 0x0, ttl 60, id 24170, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000032 IP (tos 0x0, ttl 57, id 29523, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 60, id 24171, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000039 IP (tos 0x0, ttl 60, id 24172, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000022 IP (tos 0x0, ttl 57, id 29524, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 60, id 24173, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000039 IP (tos 0x0, ttl 60, id 24174, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000040 IP (tos 0x0, ttl 60, id 24175, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000037 IP (tos 0x0, ttl 60, id 24176, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000047 IP (tos 0x0, ttl 60, id 24177, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000020 IP (tos 0x0, ttl 57, id 29525, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 60, id 24178, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000038 IP (tos 0x0, ttl 60, id 24179, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000037 IP (tos 0x0, ttl 60, id 24180, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000032 IP (tos 0x0, ttl 60, id 24181, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000027 IP (tos 0x0, ttl 60, id 24182, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000035 IP (tos 0x0, ttl 60, id 24183, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000026 IP (tos 0x0, ttl 57, id 29526, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000033 IP (tos 0x0, ttl 60, id 24184, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000157 IP (tos 0x0, ttl 57, id 29527, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000023 IP (tos 0x0, ttl 60, id 24185, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000034 IP (tos 0x0, ttl 60, id 24186, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000058 IP (tos 0x0, ttl 60, id 24187, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 57, id 29528, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000024 IP (tos 0x0, ttl 60, id 24188, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000068 IP (tos 0x0, ttl 57, id 29529, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 60, id 24189, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 57, id 29530, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000032 IP (tos 0x0, ttl 60, id 24190, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000031 IP (tos 0x0, ttl 60, id 24191, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29531, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29532, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29533, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29534, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29535, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000007 IP (tos 0x0, ttl 57, id 29536, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29537, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29538, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29539, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29540, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 57, id 29541, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29542, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29543, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000061 IP (tos 0x0, ttl 57, id 29544, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000023 IP (tos 0x0, ttl 60, id 24192, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29545, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000022 IP (tos 0x0, ttl 60, id 24193, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000035 IP (tos 0x0, ttl 60, id 24194, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000036 IP (tos 0x0, ttl 57, id 29546, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000025 IP (tos 0x0, ttl 60, id 24195, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000036 IP (tos 0x0, ttl 60, id 24196, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29547, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24197, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000033 IP (tos 0x0, ttl 60, id 24198, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 60, id 24199, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 57, id 29548, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000021 IP (tos 0x0, ttl 57, id 29549, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24200, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000021 IP (tos 0x0, ttl 57, id 29550, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000026 IP (tos 0x0, ttl 60, id 24201, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29551, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000029 IP (tos 0x0, ttl 57, id 29552, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 60, id 24202, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000036 IP (tos 0x0, ttl 60, id 24203, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29553, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24204, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000031 IP (tos 0x0, ttl 60, id 24205, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000029 IP (tos 0x0, ttl 60, id 24206, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000026 IP (tos 0x0, ttl 57, id 29554, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 60, id 24207, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 57, id 29555, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 60, id 24208, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000030 IP (tos 0x0, ttl 57, id 29556, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 60, id 24209, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000029 IP (tos 0x0, ttl 57, id 29557, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24210, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 57, id 29558, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000023 IP (tos 0x0, ttl 60, id 24211, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29559, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000062 IP (tos 0x0, ttl 57, id 29560, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000009 IP (tos 0x0, ttl 57, id 29561, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000006 IP (tos 0x0, ttl 57, id 29562, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24212, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29563, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24213, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000026 IP (tos 0x0, ttl 57, id 29564, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000027 IP (tos 0x0, ttl 60, id 24214, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000031 IP (tos 0x0, ttl 57, id 29565, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000027 IP (tos 0x0, ttl 60, id 24215, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000031 IP (tos 0x0, ttl 57, id 29566, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24216, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000041 IP (tos 0x0, ttl 60, id 24217, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000029 IP (tos 0x0, ttl 60, id 24218, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29567, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29568, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24219, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29569, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 60, id 24220, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000029 IP (tos 0x0, ttl 60, id 24221, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000024 IP (tos 0x0, ttl 60, id 24222, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29570, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 60, id 24223, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29571, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 60, id 24224, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 60, id 24225, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000021 IP (tos 0x0, ttl 57, id 29572, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 60, id 24226, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000024 IP (tos 0x0, ttl 57, id 29573, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000022 IP (tos 0x0, ttl 60, id 24227, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29574, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 60, id 24228, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29575, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000061 IP (tos 0x0, ttl 57, id 29576, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000009 IP (tos 0x0, ttl 57, id 29577, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000027 IP (tos 0x0, ttl 60, id 24229, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 60, id 24230, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 57, id 29578, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24231, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 60, id 24232, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000022 IP (tos 0x0, ttl 57, id 29579, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000027 IP (tos 0x0, ttl 60, id 24233, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29580, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 60, id 24234, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29581, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24235, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24236, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29582, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 60, id 24237, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000017 IP (tos 0x0, ttl 57, id 29583, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 60, id 24238, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 60, id 24239, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29584, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 60, id 24240, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29585, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24241, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29586, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24242, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29587, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000009 IP (tos 0x0, ttl 57, id 29588, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29589, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000007 IP (tos 0x0, ttl 57, id 29590, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29591, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000057 IP (tos 0x0, ttl 57, id 29592, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29593, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 60, id 24243, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000020 IP (tos 0x0, ttl 60, id 24244, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000037 IP (tos 0x0, ttl 60, id 24245, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000030 IP (tos 0x0, ttl 60, id 24246, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29594, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 60, id 24247, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000026 IP (tos 0x0, ttl 60, id 24248, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000130 IP (tos 0x0, ttl 60, id 24249, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000021 IP (tos 0x0, ttl 57, id 29595, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24250, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000032 IP (tos 0x0, ttl 60, id 24251, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000026 IP (tos 0x0, ttl 60, id 24252, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000020 IP (tos 0x0, ttl 60, id 24253, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29596, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000034 IP (tos 0x0, ttl 57, id 29597, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000025 IP (tos 0x0, ttl 60, id 24254, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000037 IP (tos 0x0, ttl 60, id 24255, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29598, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24256, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000026 IP (tos 0x0, ttl 57, id 29599, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 57, id 29600, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 60, id 24257, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000017 IP (tos 0x0, ttl 57, id 29601, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29602, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29603, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29604, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29605, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29606, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29607, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000059 IP (tos 0x0, ttl 57, id 29608, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29609, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000031 IP (tos 0x0, ttl 60, id 24258, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 60, id 24259, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29610, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 57, id 29611, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24260, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000035 IP (tos 0x0, ttl 60, id 24261, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29612, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24262, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000033 IP (tos 0x0, ttl 60, id 24263, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000027 IP (tos 0x0, ttl 60, id 24264, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000024 IP (tos 0x0, ttl 60, id 24265, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29613, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000024 IP (tos 0x0, ttl 60, id 24266, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000009 IP (tos 0x0, ttl 57, id 29614, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24267, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 60, id 24268, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000020 IP (tos 0x0, ttl 57, id 29615, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24269, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000030 IP (tos 0x0, ttl 60, id 24270, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24271, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29616, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24272, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 57, id 29617, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29618, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29619, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29620, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29621, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29622, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29623, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000057 IP (tos 0x0, ttl 57, id 29624, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000027 IP (tos 0x0, ttl 60, id 24273, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 60, id 24274, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29625, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000026 IP (tos 0x0, ttl 60, id 24275, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29626, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000022 IP (tos 0x0, ttl 60, id 24276, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000017 IP (tos 0x0, ttl 57, id 29627, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000023 IP (tos 0x0, ttl 60, id 24277, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000040 IP (tos 0x0, ttl 60, id 24278, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000033 IP (tos 0x0, ttl 60, id 24279, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 60, id 24280, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000026 IP (tos 0x0, ttl 60, id 24281, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29628, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24282, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000032 IP (tos 0x0, ttl 60, id 24283, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000037 IP (tos 0x0, ttl 60, id 24284, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000021 IP (tos 0x0, ttl 57, id 29629, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29630, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 60, id 24285, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000029 IP (tos 0x0, ttl 60, id 24286, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 57, id 29631, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24287, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000030 IP (tos 0x0, ttl 57, id 29632, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 60, id 24288, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 57, id 29633, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29634, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29635, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000008 IP (tos 0x0, ttl 57, id 29636, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29637, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29638, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29639, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000056 IP (tos 0x0, ttl 57, id 29640, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29641, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000025 IP (tos 0x0, ttl 60, id 24289, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 60, id 24290, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 57, id 29642, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24291, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000035 IP (tos 0x0, ttl 60, id 24292, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29643, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000022 IP (tos 0x0, ttl 60, id 24293, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000039 IP (tos 0x0, ttl 60, id 24294, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000034 IP (tos 0x0, ttl 60, id 24295, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000027 IP (tos 0x0, ttl 60, id 24296, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29644, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000027 IP (tos 0x0, ttl 57, id 29645, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000032 IP (tos 0x0, ttl 57, id 29646, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000031 IP (tos 0x0, ttl 57, id 29647, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29648, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000024 IP (tos 0x0, ttl 60, id 24297, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000027 IP (tos 0x0, ttl 57, id 29649, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000026 IP (tos 0x0, ttl 60, id 24298, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29650, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 60, id 24299, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000022 IP (tos 0x0, ttl 57, id 29651, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000022 IP (tos 0x0, ttl 60, id 24300, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000027 IP (tos 0x0, ttl 60, id 24301, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29652, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 60, id 24302, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000026 IP (tos 0x0, ttl 57, id 29653, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29654, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29655, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000054 IP (tos 0x0, ttl 57, id 29656, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29657, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 57, id 29658, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000025 IP (tos 0x0, ttl 60, id 24303, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29659, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000008 IP (tos 0x0, ttl 57, id 29660, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24304, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000020 IP (tos 0x0, ttl 57, id 29661, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000009 IP (tos 0x0, ttl 57, id 29662, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24305, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29663, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29664, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24306, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29665, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24307, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29666, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29667, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24308, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29668, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29669, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 60, id 24309, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29670, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24310, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000021 IP (tos 0x0, ttl 57, id 29671, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 60, id 24311, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000035 IP (tos 0x0, ttl 60, id 24312, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 57, id 29672, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000086 IP (tos 0x0, ttl 57, id 29673, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000022 IP (tos 0x0, ttl 60, id 24313, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29674, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 60, id 24314, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29675, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29676, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 60, id 24315, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000024 IP (tos 0x0, ttl 57, id 29677, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 60, id 24316, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29678, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24317, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29679, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29680, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 60, id 24318, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29681, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29682, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29683, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29684, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29685, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29686, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29687, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000058 IP (tos 0x0, ttl 57, id 29688, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29689, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000045 IP (tos 0x0, ttl 60, id 24319, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000021 IP (tos 0x0, ttl 57, id 29690, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000033 IP (tos 0x0, ttl 60, id 24320, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 57, id 29691, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000032 IP (tos 0x0, ttl 60, id 24321, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000029 IP (tos 0x0, ttl 57, id 29692, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000026 IP (tos 0x0, ttl 60, id 24322, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000031 IP (tos 0x0, ttl 60, id 24323, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29693, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24324, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000033 IP (tos 0x0, ttl 60, id 24325, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000034 IP (tos 0x0, ttl 60, id 24326, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 57, id 29694, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000023 IP (tos 0x0, ttl 60, id 24327, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 57, id 29695, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000029 IP (tos 0x0, ttl 60, id 24328, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000034 IP (tos 0x0, ttl 60, id 24329, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29696, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24330, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000031 IP (tos 0x0, ttl 60, id 24331, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000037 IP (tos 0x0, ttl 60, id 24332, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000017 IP (tos 0x0, ttl 57, id 29697, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29698, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24333, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000029 IP (tos 0x0, ttl 60, id 24334, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000035 IP (tos 0x0, ttl 60, id 24335, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000032 IP (tos 0x0, ttl 60, id 24336, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29699, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 60, id 24337, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000041 IP (tos 0x0, ttl 60, id 24338, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000037 IP (tos 0x0, ttl 60, id 24339, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 57, id 29700, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24340, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000027 IP (tos 0x0, ttl 57, id 29701, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 60, id 24341, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000034 IP (tos 0x0, ttl 60, id 24342, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000033 IP (tos 0x0, ttl 60, id 24343, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000022 IP (tos 0x0, ttl 57, id 29702, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 60, id 24344, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000029 IP (tos 0x0, ttl 60, id 24345, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000021 IP (tos 0x0, ttl 57, id 29703, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 60, id 24346, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000068 IP (tos 0x0, ttl 60, id 24347, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000003 IP (tos 0x0, ttl 57, id 29704, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000022 IP (tos 0x0, ttl 57, id 29705, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 60, id 24348, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000029 IP (tos 0x0, ttl 57, id 29706, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000022 IP (tos 0x0, ttl 60, id 24349, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000039 IP (tos 0x0, ttl 60, id 24350, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000039 IP (tos 0x0, ttl 60, id 24351, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000033 IP (tos 0x0, ttl 60, id 24352, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000028 IP (tos 0x0, ttl 57, id 29707, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000025 IP (tos 0x0, ttl 60, id 24353, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000027 IP (tos 0x0, ttl 60, id 24354, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000020 IP (tos 0x0, ttl 57, id 29708, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24355, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000025 IP (tos 0x0, ttl 57, id 29709, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000026 IP (tos 0x0, ttl 60, id 24356, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000024 IP (tos 0x0, ttl 57, id 29710, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24357, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000027 IP (tos 0x0, ttl 57, id 29711, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24358, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29712, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 57, id 29713, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 57, id 29714, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000018 IP (tos 0x0, ttl 57, id 29715, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29716, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29717, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000010 IP (tos 0x0, ttl 57, id 29718, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29719, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000054 IP (tos 0x0, ttl 57, id 29720, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29721, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29722, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000034 IP (tos 0x0, ttl 60, id 24359, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000034 IP (tos 0x0, ttl 57, id 29723, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000020 IP (tos 0x0, ttl 60, id 24360, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000023 IP (tos 0x0, ttl 57, id 29724, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24361, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000016 IP (tos 0x0, ttl 57, id 29725, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000012 IP (tos 0x0, ttl 57, id 29726, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 57, id 29727, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29728, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29729, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29730, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000013 IP (tos 0x0, ttl 57, id 29731, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29732, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000011 IP (tos 0x0, ttl 57, id 29733, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000014 IP (tos 0x0, ttl 57, id 29734, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000015 IP (tos 0x0, ttl 57, id 29735, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000065 IP (tos 0x0, ttl 57, id 29736, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000008 IP (tos 0x0, ttl 57, id 29737, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000023 IP (tos 0x0, ttl 60, id 24362, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000036 IP (tos 0x0, ttl 60, id 24363, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000020 IP (tos 0x0, ttl 57, id 29738, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000031 IP (tos 0x0, ttl 60, id 24364, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000036 IP (tos 0x0, ttl 60, id 24365, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000022 IP (tos 0x0, ttl 57, id 29739, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000016 IP (tos 0x0, ttl 60, id 24366, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000019 IP (tos 0x0, ttl 57, id 29740, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000017 IP (tos 0x0, ttl 60, id 24367, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000017 IP (tos 0x0, ttl 57, id 29741, offset 0, flags [DF], length:
    180) loncmxs1024.1747962266 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000019 IP (tos 0x0, ttl 60, id 24368, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]
    000021 IP (tos 0x0, ttl 60, id 24369, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    POST: [|nfs]



    Thats not all of it, but bear in mind a succesfull mount only spits
    one or two lines from the server dump,

    IE, this is all I get from a succesfull mount
    000039 IP (tos 0x0, ttl 57, id 59038, offset 0, flags [DF], length:
    84) loncmxs1036-bck.1184091157 > loncmxs1018.nfs: 44 null
    000099 IP (tos 0x0, ttl 57, id 59045, offset 0, flags [DF], length:
    180) loncmxs1036-bck.1303360816 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    000134 IP (tos 0x0, ttl 60, id 31463, offset 0, flags [DF], length:
    208) loncmxs1018.nfs > loncmxs1036-bck.1303360816: reply ok 168 fsinfo
    POST: [|nfs]



    Can anyone pick the peanuts out of those dumps and find a clue?

    Much appreciated,

    Matt.


  7. Re: nfsmnthelp holding up server nfsd?

    MattWarren wrote:
    > On 5 Jul, 17:40, MattWarren wrote:
    >> On 5 Jul, 17:22, MattWarren wrote:
    >>
    >>
    >>
    >>
    >>
    >>> On 5 Jul, 17:07, Hajo Ehlers wrote:
    >>>> What are the option for
    >>>> nfsd
    >>>> rpc.mountd
    >>>> Not that you use the -c option for the nfsd or -N for the rpc.mountd
    >>>> On the client as well as on the server itself issue a
    >>>> $ showmount -e NFSSERVER
    >>>> and see what happens.
    >>>> hth
    >>>> Hajo
    >>> Hi,
    >>> RPC etc.. all seems to be fine and reporting as it should;
    >>> from client
    >>> root@jinglebells:/apps/sys/bin> showmount -e twinkletoes
    >>> export list for twinkletoes:
    >>> /tmp/invscout (everyone)

    > 000033 IP (tos 0x0, ttl 60, id 24352, offset 0, flags [DF], length:
    > 208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    > POST: [|nfs]


    > 000021 IP (tos 0x0, ttl 60, id 24369, offset 0, flags [DF], length:
    > 208) loncmxs1018.nfs > loncmxs1024.1747962266: reply ok 168 fsinfo
    > POST: [|nfs]
    >
    >
    >
    > Thats not all of it, but bear in mind a succesfull mount only spits
    > one or two lines from the server dump,
    >
    > IE, this is all I get from a succesfull mount
    > 000039 IP (tos 0x0, ttl 57, id 59038, offset 0, flags [DF], length:
    > 84) loncmxs1036-bck.1184091157 > loncmxs1018.nfs: 44 null
    > 000099 IP (tos 0x0, ttl 57, id 59045, offset 0, flags [DF], length:
    > 180) loncmxs1036-bck.1303360816 > loncmxs1018.nfs: 140 fsinfo [|nfs]
    > 000134 IP (tos 0x0, ttl 60, id 31463, offset 0, flags [DF], length:
    > 208) loncmxs1018.nfs > loncmxs1036-bck.1303360816: reply ok 168 fsinfo
    > POST: [|nfs]
    >
    >
    >
    > Can anyone pick the peanuts out of those dumps and find a clue?
    >
    > Much appreciated,
    >
    > Matt.
    >

    Compare the DNS resolution for the servers that work and the ones that
    don't. Make sure you have long/short/gethostbyname/
    gethostbyaddr all set up correctly.

  8. Re: nfsmnthelp holding up server nfsd?

    On Jul 5, 6:22 pm, MattWarren wrote:
    ....
    > understanding exactly what a badcall is will give further
    > clues...



    >From the redbook

    AIX 5L Practical Performance Tools and Tuning Guide SG24-6478-00
    ....
    badcalls Total number of calls rejected by the RPC layer. The rejects
    happen because of failed authentication. The value should be zero.

    So check your DNS ( resolve via hostname / ip from both sides ) ,
    check with entstat that you have on the client side no corrupted
    network packages and of cource any kind of router/firewall in between.

    hth
    Hajo


  9. Re: nfsmnthelp holding up server nfsd?

    On Jul 6, 8:53 am, Hajo Ehlers wrote:
    > On Jul 5, 6:22 pm, MattWarren wrote:
    > ...
    >
    > > understanding exactly what a badcall is will give further
    > > clues...
    > >From the redbook

    >
    > AIX 5L Practical Performance Tools and Tuning Guide SG24-6478-00
    > ...
    > badcalls Total number of calls rejected by the RPC layer. The rejects
    > happen because of failed authentication. The value should be zero.
    >
    > So check your DNS ( resolve via hostname / ip from both sides ) ,
    > check with entstat that you have on the client side no corrupted
    > network packages and of cource any kind of router/firewall in between.
    >
    > hth
    > Hajo


    Hi,

    DNS is fine on both sides, hostname->ip ip->hostname

    I can see this in a netpmon;
    On the server:
    Detailed NFSv3 Server Statistics (by Client):
    ---------------------------------------------

    CLIENT: loncmxs1024
    other calls: 2043
    other times (msec): avg 36095.581 min 27608.409 max 36212.573 sdev
    197.146


    on the Client:
    Detailed NFS Client RPC Statistics (by Server):
    -----------------------------------------------

    SERVER: loncmxs1018.uk.net.intra
    calls: 1
    call times (msec): avg 1.120 min 1.120 max 1.120 sdev 0.000



    That was after 60 secs of monitoring immediatley the client requested
    a mount from the server.

    Huge response times. So far this is the only way I can get real
    numbers out of the machine that show a problem!

    I have also noticed in nfsstat on the client:

    nfsstat -c

    Client rpc:
    Connection oriented
    calls badcalls badxids timeouts newcreds badverfs
    timers
    510140 510107 0 510000 0 0 0
    nomem cantconn interrupts
    0 107 0
    Connectionless
    calls badcalls retrans badxids timeouts newcreds
    badverfs
    70 0 0 0 0 0 0
    timers nomem cantsend
    0 0 0

    Client nfs:
    calls badcalls clgets cltoomany
    77 41 0 0
    Version 2: (0 calls)
    null getattr setattr root lookup readlink read
    0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
    wrcache write create remove rename link
    symlink
    0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
    mkdir rmdir readdir statfs
    0 0% 0 0% 0 0% 0 0%
    Version 3: (77 calls)
    null getattr setattr lookup access readlink read
    0 0% 7 9% 0 0% 0 0% 10 12% 0 0% 0 0%
    write create mkdir symlink mknod remove
    rmdir
    0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
    rename link readdir readdir+ fsstat fsinfo
    pathconf
    0 0% 0 0% 0 0% 15 19% 1 1% 44 57% 0 0%
    commit
    0 0%


    the vast majority of badcalls are in the rpc layer on the client.

    the server nfsstat gives

    nfsstat -s


    Server rpc:
    Connection oriented
    calls badcalls nullrecv badlen xdrcall dupchecks
    dupreqs
    12329545 0 0 0 0 6268453 173
    Connectionless
    calls badcalls nullrecv badlen xdrcall dupchecks
    dupreqs
    97144 0 0 0 0 90462 368

    Server nfs:
    calls badcalls public_v2 public_v3
    12426665 4200857 0 0
    Version 2: (4 calls)
    null getattr setattr root lookup readlink read
    1 25% 1 25% 0 0% 0 0% 0 0% 0 0% 1
    25%
    wrcache write create remove rename link
    symlink
    0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
    mkdir rmdir readdir statfs
    0 0% 0 0% 0 0% 1 25%
    Version 3: (12426661 calls)
    null getattr setattr lookup access readlink read
    1197 0% 299110 2% 132 0% 161346 1% 30348 0% 833 0%
    391767 3%
    write create mkdir symlink mknod remove
    rmdir
    6350239 51% 465 0% 0 0% 0 0% 0 0% 470 0% 0 0%
    rename link readdir readdir+ fsstat fsinfo
    pathconf
    0 0% 0 0% 1862 0% 7609 0% 3591 0% 4278148 34% 0
    0%
    commit
    899544 7%


    with all the badcalls in nfs not rpc.

    So i really do have a problem. but what or where is creating it I'm
    not sure.

    I have looked into RPC authentication to find the casue of the
    badcalls, but we are using AUTH_UNIX. I am root, and in less than 16
    groups. As far as I understand the 'authentication' in RPC works by
    just sending gorups and uid numbers and the server uses them to
    determine permissions?

    There shouldn't be any permissions issues for root with the filesystem
    I am trying to mount, and they are exported with permission for root
    to mount them.

    Any ideas as to how I could probe the Auth process and perhaps see if
    there is a permissions issue coming from the server would be great?


    Thanks,

    Matt.


  10. Re: nfsmnthelp holding up server nfsd?

    On Jul 6, 12:38 pm, MattWarren wrote:
    > On Jul 6, 8:53 am, Hajo Ehlers wrote:


    ....
    > I can see this in a netpmon;
    > On the server:
    > Detailed NFSv3 Server Statistics (by Client):
    > ---------------------------------------------
    >
    > CLIENT: loncmxs1024
    > other calls: 2043
    > other times (msec): avg 36095.581 min 27608.409 max 36212.573

    ....
    > Huge response times. So far this is the only way I can get real
    > numbers out of the machine that show a problem!
    >
    > Client rpc:
    > Connection oriented
    > calls badcalls badxids timeouts newcreds badverfs
    > timers
    > 510140 510107 0 510000 0 0


    You should really check for the timeout instead of the badcalls.
    For trouble-shooting:

    1) Client
    a) Mount a localy exported Filesystem via NFS
    - NFS is working at all or not
    b) Mount the nfs export from the server via udp
    - If it work check for network problems ( back hole - router , wrong
    adpater settings )
    c) Mount from a NFS server wihin the same subnet
    d) Check the ethernet adapter for errors ( entstat )
    e) Do a simple performance test between the server and the client
    Server: ftp client
    put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    Client: ftp Server
    put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    f) Try to mount nfs share on the server from a differnet client within
    the same subnet as the trouble causing client.

    2) Server
    a) Do step 1 also on the server ( I have seen that a server who was
    able to serve the current connections but was unable to provide
    service for new ones)

    hth
    Hajo


  11. Re: nfsmnthelp holding up server nfsd?

    On 6 Jul, 13:05, Hajo Ehlers wrote:
    > On Jul 6, 12:38 pm, MattWarren wrote:
    >
    > > On Jul 6, 8:53 am, Hajo Ehlers wrote:

    >
    > ...
    >
    >
    >
    >
    >
    > > I can see this in a netpmon;
    > > On the server:
    > > Detailed NFSv3 Server Statistics (by Client):
    > > ---------------------------------------------

    >
    > > CLIENT: loncmxs1024
    > > other calls: 2043
    > > other times (msec): avg 36095.581 min 27608.409 max 36212.573

    > ...
    > > Huge response times. So far this is the only way I can get real
    > > numbers out of the machine that show a problem!

    >
    > > Client rpc:
    > > Connection oriented
    > > calls badcalls badxids timeouts newcreds badverfs
    > > timers
    > > 510140 510107 0 510000 0 0

    >
    > You should really check for the timeout instead of the badcalls.
    > For trouble-shooting:
    >
    > 1) Client
    > a) Mount a localy exported Filesystem via NFS
    > - NFS is working at all or not
    > b) Mount the nfs export from the server via udp
    > - If it work check for network problems ( back hole - router , wrong
    > adpater settings )
    > c) Mount from a NFS server wihin the same subnet
    > d) Check the ethernet adapter for errors ( entstat )
    > e) Do a simple performance test between the server and the client
    > Server: ftp client
    > put "| dd if=/dev/zero bs=32k count=1000" /dev/null
    >
    > Client: ftp Server
    > put "| dd if=/dev/zero bs=32k count=1000" /dev/null
    >
    > f) Try to mount nfs share on the server from a differnet client within
    > the same subnet as the trouble causing client.
    >
    > 2) Server
    > a) Do step 1 also on the server ( I have seen that a server who was
    > able to serve the current connections but was unable to provide
    > service for new ones)
    >
    > hth
    > Hajo- Hide quoted text -
    >
    > - Show quoted text -


    I was getting all wrapped up in the problem and forgetting to stand
    back and take it one step at a time ..

    TCP mounts to locally exported filesystem fail with the same error.
    UDP mounts both to the local system and the remote server work fine.

    I'm off to find out what can cause it, but if you have any
    pointers..


    Thanks for your help


    Matt.


  12. Re: nfsmnthelp holding up server nfsd?

    On 6 Jul, 13:17, MattWarren wrote:
    > On 6 Jul, 13:05, Hajo Ehlers wrote:
    >
    >
    >
    >
    >
    > > On Jul 6, 12:38 pm, MattWarren wrote:

    >
    > > > On Jul 6, 8:53 am, Hajo Ehlers wrote:

    >
    > > ...

    >
    > > > I can see this in a netpmon;
    > > > On the server:
    > > > Detailed NFSv3 Server Statistics (by Client):
    > > > ---------------------------------------------

    >
    > > > CLIENT: loncmxs1024
    > > > other calls: 2043
    > > > other times (msec): avg 36095.581 min 27608.409 max 36212.573

    > > ...
    > > > Huge response times. So far this is the only way I can get real
    > > > numbers out of the machine that show a problem!

    >
    > > > Client rpc:
    > > > Connection oriented
    > > > calls badcalls badxids timeouts newcreds badverfs
    > > > timers
    > > > 510140 510107 0 510000 0 0

    >
    > > You should really check for the timeout instead of the badcalls.
    > > For trouble-shooting:

    >
    > > 1) Client
    > > a) Mount a localy exported Filesystem via NFS
    > > - NFS is working at all or not
    > > b) Mount the nfs export from the server via udp
    > > - If it work check for network problems ( back hole - router , wrong
    > > adpater settings )
    > > c) Mount from a NFS server wihin the same subnet
    > > d) Check the ethernet adapter for errors ( entstat )
    > > e) Do a simple performance test between the server and the client
    > > Server: ftp client
    > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > Client: ftp Server
    > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > f) Try to mount nfs share on the server from a differnet client within
    > > the same subnet as the trouble causing client.

    >
    > > 2) Server
    > > a) Do step 1 also on the server ( I have seen that a server who was
    > > able to serve the current connections but was unable to provide
    > > service for new ones)

    >
    > > hth
    > > Hajo- Hide quoted text -

    >
    > > - Show quoted text -

    >
    > I was getting all wrapped up in the problem and forgetting to stand
    > back and take it one step at a time ..
    >
    > TCP mounts to locally exported filesystem fail with the same error.
    > UDP mounts both to the local system and the remote server work fine.
    >
    > I'm off to find out what can cause it, but if you have any
    > pointers..
    >
    > Thanks for your help
    >
    > Matt.- Hide quoted text -
    >
    > - Show quoted text -


    TCP mounts from other clients to the server work.

    Other problem clients have the same behaviour, some exist on different
    networks. Working and Non-working clients can be found on the same
    networks.

    all problem clients work with UDP but not TCP.

    entstat shows no errors, ftp tests run fine.

    matt


  13. Re: nfsmnthelp holding up server nfsd?

    On 6 Jul, 13:32, MattWarren wrote:
    > On 6 Jul, 13:17, MattWarren wrote:
    >
    >
    >
    >
    >
    > > On 6 Jul, 13:05, Hajo Ehlers wrote:

    >
    > > > On Jul 6, 12:38 pm, MattWarren wrote:

    >
    > > > > On Jul 6, 8:53 am, Hajo Ehlers wrote:

    >
    > > > ...

    >
    > > > > I can see this in a netpmon;
    > > > > On the server:
    > > > > Detailed NFSv3 Server Statistics (by Client):
    > > > > ---------------------------------------------

    >
    > > > > CLIENT: loncmxs1024
    > > > > other calls: 2043
    > > > > other times (msec): avg 36095.581 min 27608.409 max 36212.573
    > > > ...
    > > > > Huge response times. So far this is the only way I can get real
    > > > > numbers out of the machine that show a problem!

    >
    > > > > Client rpc:
    > > > > Connection oriented
    > > > > calls badcalls badxids timeouts newcreds badverfs
    > > > > timers
    > > > > 510140 510107 0 510000 0 0

    >
    > > > You should really check for the timeout instead of the badcalls.
    > > > For trouble-shooting:

    >
    > > > 1) Client
    > > > a) Mount a localy exported Filesystem via NFS
    > > > - NFS is working at all or not
    > > > b) Mount the nfs export from the server via udp
    > > > - If it work check for network problems ( back hole - router , wrong
    > > > adpater settings )
    > > > c) Mount from a NFS server wihin the same subnet
    > > > d) Check the ethernet adapter for errors ( entstat )
    > > > e) Do a simple performance test between the server and the client
    > > > Server: ftp client
    > > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > > Client: ftp Server
    > > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > > f) Try to mount nfs share on the server from a differnet client within
    > > > the same subnet as the trouble causing client.

    >
    > > > 2) Server
    > > > a) Do step 1 also on the server ( I have seen that a server who was
    > > > able to serve the current connections but was unable to provide
    > > > service for new ones)

    >
    > > > hth
    > > > Hajo- Hide quoted text -

    >
    > > > - Show quoted text -

    >
    > > I was getting all wrapped up in the problem and forgetting to stand
    > > back and take it one step at a time ..

    >
    > > TCP mounts to locally exported filesystem fail with the same error.
    > > UDP mounts both to the local system and the remote server work fine.

    >
    > > I'm off to find out what can cause it, but if you have any
    > > pointers..

    >
    > > Thanks for your help

    >
    > > Matt.- Hide quoted text -

    >
    > > - Show quoted text -

    >
    > TCP mounts from other clients to the server work.
    >
    > Other problem clients have the same behaviour, some exist on different
    > networks. Working and Non-working clients can be found on the same
    > networks.
    >
    > all problem clients work with UDP but not TCP.
    >
    > entstat shows no errors, ftp tests run fine.
    >
    > matt- Hide quoted text -
    >
    > - Show quoted text -


    While a failed TCP mount is in progress, this can bee seen on the
    server,

    Proto Recv-Q Send-Q Local Address Foreign Address
    (state)
    tcp4 600032 343948 loncmxs1018.shilp loncmxs1008.34641
    ESTABLISHED

    A huge Recv-Q and Send-Q, and it stays like that. The client appears
    hung with:
    NFS server loncmxs1018 not responding still trying


  14. Re: nfsmnthelp holding up server nfsd?

    On Jul 6, 2:42 pm, MattWarren wrote:
    > On 6 Jul, 13:32, MattWarren wrote:
    >
    >
    >
    > > On 6 Jul, 13:17, MattWarren wrote:

    >
    > > > On 6 Jul, 13:05, Hajo Ehlers wrote:

    >
    > > > > On Jul 6, 12:38 pm, MattWarren wrote:

    >
    > > > > > On Jul 6, 8:53 am, Hajo Ehlers wrote:

    >
    > > > > ...

    >
    > > > > > I can see this in a netpmon;
    > > > > > On the server:
    > > > > > Detailed NFSv3 Server Statistics (by Client):
    > > > > > ---------------------------------------------

    >
    > > > > > CLIENT: loncmxs1024
    > > > > > other calls: 2043
    > > > > > other times (msec): avg 36095.581 min 27608.409 max 36212.573
    > > > > ...
    > > > > > Huge response times. So far this is the only way I can get real
    > > > > > numbers out of the machine that show a problem!

    >
    > > > > > Client rpc:
    > > > > > Connection oriented
    > > > > > calls badcalls badxids timeouts newcreds badverfs
    > > > > > timers
    > > > > > 510140 510107 0 510000 0 0

    >
    > > > > You should really check for the timeout instead of the badcalls.
    > > > > For trouble-shooting:

    >
    > > > > 1) Client
    > > > > a) Mount a localy exported Filesystem via NFS
    > > > > - NFS is working at all or not
    > > > > b) Mount the nfs export from the server via udp
    > > > > - If it work check for network problems ( back hole - router , wrong
    > > > > adpater settings )
    > > > > c) Mount from a NFS server wihin the same subnet
    > > > > d) Check the ethernet adapter for errors ( entstat )
    > > > > e) Do a simple performance test between the server and the client
    > > > > Server: ftp client
    > > > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > > > Client: ftp Server
    > > > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > > > f) Try to mount nfs share on the server from a differnet client within
    > > > > the same subnet as the trouble causing client.

    >
    > > > > 2) Server
    > > > > a) Do step 1 also on the server ( I have seen that a server who was
    > > > > able to serve the current connections but was unable to provide
    > > > > service for new ones)

    >
    > > > > hth
    > > > > Hajo- Hide quoted text -

    >
    > > > > - Show quoted text -

    >
    > > > I was getting all wrapped up in the problem and forgetting to stand
    > > > back and take it one step at a time ..

    >
    > > > TCP mounts to locally exported filesystem fail with the same error.
    > > > UDP mounts both to the local system and the remote server work fine.

    >
    > > > I'm off to find out what can cause it, but if you have any
    > > > pointers..

    >
    > > > Thanks for your help

    >
    > > > Matt.- Hide quoted text -

    >
    > > > - Show quoted text -

    >
    > > TCP mounts from other clients to the server work.

    >
    > > Other problem clients have the same behaviour, some exist on different
    > > networks. Working and Non-working clients can be found on the same
    > > networks.

    >
    > > all problem clients work with UDP but not TCP.

    >
    > > entstat shows no errors, ftp tests run fine.

    >
    > > matt- Hide quoted text -

    >
    > > - Show quoted text -

    >
    > While a failed TCP mount is in progress, this can bee seen on the
    > server,
    >
    > Proto Recv-Q Send-Q Local Address Foreign Address
    > (state)
    > tcp4 600032 343948 loncmxs1018.shilp loncmxs1008.34641
    > ESTABLISHED
    >
    > A huge Recv-Q and Send-Q, and it stays like that. The client appears
    > hung with:
    > NFS server loncmxs1018 not responding still trying


    Compare the output of the
    "no -a" and "nfso -a" comannds and check as well with "lsattr -El
    en0" the MTU size with a different and working aix 5.1 client

    hth
    Hajo


  15. Re: nfsmnthelp holding up server nfsd?

    On 6 Jul, 14:18, Hajo Ehlers wrote:
    > On Jul 6, 2:42 pm, MattWarren wrote:
    >
    >
    >
    >
    >
    > > On 6 Jul, 13:32, MattWarren wrote:

    >
    > > > On 6 Jul, 13:17, MattWarren wrote:

    >
    > > > > On 6 Jul, 13:05, Hajo Ehlers wrote:

    >
    > > > > > On Jul 6, 12:38 pm, MattWarren wrote:

    >
    > > > > > > On Jul 6, 8:53 am, Hajo Ehlers wrote:

    >
    > > > > > ...

    >
    > > > > > > I can see this in a netpmon;
    > > > > > > On the server:
    > > > > > > Detailed NFSv3 Server Statistics (by Client):
    > > > > > > ---------------------------------------------

    >
    > > > > > > CLIENT: loncmxs1024
    > > > > > > other calls: 2043
    > > > > > > other times (msec): avg 36095.581 min 27608.409 max 36212.573
    > > > > > ...
    > > > > > > Huge response times. So far this is the only way I can get real
    > > > > > > numbers out of the machine that show a problem!

    >
    > > > > > > Client rpc:
    > > > > > > Connection oriented
    > > > > > > calls badcalls badxids timeouts newcreds badverfs
    > > > > > > timers
    > > > > > > 510140 510107 0 510000 0 0

    >
    > > > > > You should really check for the timeout instead of the badcalls.
    > > > > > For trouble-shooting:

    >
    > > > > > 1) Client
    > > > > > a) Mount a localy exported Filesystem via NFS
    > > > > > - NFS is working at all or not
    > > > > > b) Mount the nfs export from the server via udp
    > > > > > - If it work check for network problems ( back hole - router , wrong
    > > > > > adpater settings )
    > > > > > c) Mount from a NFS server wihin the same subnet
    > > > > > d) Check the ethernet adapter for errors ( entstat )
    > > > > > e) Do a simple performance test between the server and the client
    > > > > > Server: ftp client
    > > > > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > > > > Client: ftp Server
    > > > > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > > > > f) Try to mount nfs share on the server from a differnet client within
    > > > > > the same subnet as the trouble causing client.

    >
    > > > > > 2) Server
    > > > > > a) Do step 1 also on the server ( I have seen that a server who was
    > > > > > able to serve the current connections but was unable to provide
    > > > > > service for new ones)

    >
    > > > > > hth
    > > > > > Hajo- Hide quoted text -

    >
    > > > > > - Show quoted text -

    >
    > > > > I was getting all wrapped up in the problem and forgetting to stand
    > > > > back and take it one step at a time ..

    >
    > > > > TCP mounts to locally exported filesystem fail with the same error.
    > > > > UDP mounts both to the local system and the remote server work fine.

    >
    > > > > I'm off to find out what can cause it, but if you have any
    > > > > pointers..

    >
    > > > > Thanks for your help

    >
    > > > > Matt.- Hide quoted text -

    >
    > > > > - Show quoted text -

    >
    > > > TCP mounts from other clients to the server work.

    >
    > > > Other problem clients have the same behaviour, some exist on different
    > > > networks. Working and Non-working clients can be found on the same
    > > > networks.

    >
    > > > all problem clients work with UDP but not TCP.

    >
    > > > entstat shows no errors, ftp tests run fine.

    >
    > > > matt- Hide quoted text -

    >
    > > > - Show quoted text -

    >
    > > While a failed TCP mount is in progress, this can bee seen on the
    > > server,

    >
    > > Proto Recv-Q Send-Q Local Address Foreign Address
    > > (state)
    > > tcp4 600032 343948 loncmxs1018.shilp loncmxs1008.34641
    > > ESTABLISHED

    >
    > > A huge Recv-Q and Send-Q, and it stays like that. The client appears
    > > hung with:
    > > NFS server loncmxs1018 not responding still trying

    >
    > Compare the output of the
    > "no -a" and "nfso -a" comannds and check as well with "lsattr -El
    > en0" the MTU size with a different and working aix 5.1 client
    >
    > hth
    > Hajo- Hide quoted text -
    >
    > - Show quoted text -


    nfso options are the same, no differs by
    no=working client
    no2=failing client

    [root@loncmxs1022] # diff no no2
    2c2
    < thewall = 15852544
    ---
    > thewall = 13816832

    28c28
    < nbc_limit = 15590400
    ---
    > nbc_limit = 13554688

    32c32
    < nbc_pseg_limit = 16777184
    ---
    > nbc_pseg_limit = 14680032

    114a115

    lsattr -El en0, ent0, et0 are all the same, except the failing client
    examined has 2 IP aliases set on en0.
    Other failing clients (there are 5 in total) do not have aliases
    applied.


    >



  16. Re: nfsmnthelp holding up server nfsd?

    On Jul 6, 4:00 pm, MattWarren wrote:
    > On 6 Jul, 14:18, Hajo Ehlers wrote:
    >
    >
    >
    > > On Jul 6, 2:42 pm, MattWarren wrote:

    >
    > > > On 6 Jul, 13:32, MattWarren wrote:

    >
    > > > > On 6 Jul, 13:17, MattWarren wrote:

    >
    > > > > > On 6 Jul, 13:05, Hajo Ehlers wrote:

    >
    > > > > > > On Jul 6, 12:38 pm, MattWarren wrote:

    >
    > > > > > > > On Jul 6, 8:53 am, Hajo Ehlers wrote:

    >
    > > > > > > ...

    >
    > > > > > > > I can see this in a netpmon;
    > > > > > > > On the server:
    > > > > > > > Detailed NFSv3 Server Statistics (by Client):
    > > > > > > > ---------------------------------------------

    >
    > > > > > > > CLIENT: loncmxs1024
    > > > > > > > other calls: 2043
    > > > > > > > other times (msec): avg 36095.581 min 27608.409 max 36212.573
    > > > > > > ...
    > > > > > > > Huge response times. So far this is the only way I can get real
    > > > > > > > numbers out of the machine that show a problem!

    >
    > > > > > > > Client rpc:
    > > > > > > > Connection oriented
    > > > > > > > calls badcalls badxids timeouts newcreds badverfs
    > > > > > > > timers
    > > > > > > > 510140 510107 0 510000 0 0

    >
    > > > > > > You should really check for the timeout instead of the badcalls.
    > > > > > > For trouble-shooting:

    >
    > > > > > > 1) Client
    > > > > > > a) Mount a localy exported Filesystem via NFS
    > > > > > > - NFS is working at all or not
    > > > > > > b) Mount the nfs export from the server via udp
    > > > > > > - If it work check for network problems ( back hole - router , wrong
    > > > > > > adpater settings )
    > > > > > > c) Mount from a NFS server wihin the same subnet
    > > > > > > d) Check the ethernet adapter for errors ( entstat )
    > > > > > > e) Do a simple performance test between the server and the client
    > > > > > > Server: ftp client
    > > > > > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > > > > > Client: ftp Server
    > > > > > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > > > > > f) Try to mount nfs share on the server from a differnet client within
    > > > > > > the same subnet as the trouble causing client.

    >
    > > > > > > 2) Server
    > > > > > > a) Do step 1 also on the server ( I have seen that a server who was
    > > > > > > able to serve the current connections but was unable to provide
    > > > > > > service for new ones)

    >
    > > > > > > hth
    > > > > > > Hajo- Hide quoted text -

    >
    > > > > > > - Show quoted text -

    >
    > > > > > I was getting all wrapped up in the problem and forgetting to stand
    > > > > > back and take it one step at a time ..

    >
    > > > > > TCP mounts to locally exported filesystem fail with the same error.
    > > > > > UDP mounts both to the local system and the remote server work fine.

    >
    > > > > > I'm off to find out what can cause it, but if you have any
    > > > > > pointers..

    >
    > > > > > Thanks for your help

    >
    > > > > > Matt.- Hide quoted text -

    >
    > > > > > - Show quoted text -

    >
    > > > > TCP mounts from other clients to the server work.

    >
    > > > > Other problem clients have the same behaviour, some exist on different
    > > > > networks. Working and Non-working clients can be found on the same
    > > > > networks.

    >
    > > > > all problem clients work with UDP but not TCP.

    >
    > > > > entstat shows no errors, ftp tests run fine.

    >
    > > > > matt- Hide quoted text -

    >
    > > > > - Show quoted text -

    >
    > > > While a failed TCP mount is in progress, this can bee seen on the
    > > > server,

    >
    > > > Proto Recv-Q Send-Q Local Address Foreign Address
    > > > (state)
    > > > tcp4 600032 343948 loncmxs1018.shilp loncmxs1008.34641
    > > > ESTABLISHED

    >
    > > > A huge Recv-Q and Send-Q, and it stays like that. The client appears
    > > > hung with:
    > > > NFS server loncmxs1018 not responding still trying

    >
    > > Compare the output of the
    > > "no -a" and "nfso -a" comannds and check as well with "lsattr -El
    > > en0" the MTU size with a different and working aix 5.1 client

    >
    > > hth
    > > Hajo- Hide quoted text -

    >
    > > - Show quoted text -

    >
    > nfso options are the same, no differs by
    > no=working client
    > no2=failing client
    >
    > [root@loncmxs1022] # diff no no2
    > 2c2
    > < thewall = 15852544
    > ---> thewall = 13816832
    >
    > 28c28
    > < nbc_limit = 15590400
    > ---> nbc_limit = 13554688
    >
    > 32c32
    > < nbc_pseg_limit = 16777184
    > ---> nbc_pseg_limit = 14680032
    >
    > 114a115
    >
    > lsattr -El en0, ent0, et0 are all the same, except the failing client
    > examined has 2 IP aliases set on en0.
    > Other failing clients (there are 5 in total) do not have aliases
    > applied.
    >
    >



    Then check if the portmapper has been started after nfsd and/or the /
    etc/rpc is corrupted.

    A quick google search showes some procdure for NFS trouble shooting
    like http://web.utanet.at/mario/exam/5129cb5.htm

    Check the procedure because i would do the same.
    hth
    Hajo


  17. Re: nfsmnthelp holding up server nfsd?

    On Jul 6, 3:45 pm, Hajo Ehlers wrote:
    > On Jul 6, 4:00 pm, MattWarren wrote:
    >
    >
    >
    >
    >
    > > On 6 Jul, 14:18, Hajo Ehlers wrote:

    >
    > > > On Jul 6, 2:42 pm, MattWarren wrote:

    >
    > > > > On 6 Jul, 13:32, MattWarren wrote:

    >
    > > > > > On 6 Jul, 13:17, MattWarren wrote:

    >
    > > > > > > On 6 Jul, 13:05, Hajo Ehlers wrote:

    >
    > > > > > > > On Jul 6, 12:38 pm, MattWarren wrote:

    >
    > > > > > > > > On Jul 6, 8:53 am, Hajo Ehlers wrote:

    >
    > > > > > > > ...

    >
    > > > > > > > > I can see this in a netpmon;
    > > > > > > > > On the server:
    > > > > > > > > Detailed NFSv3 Server Statistics (by Client):
    > > > > > > > > ---------------------------------------------

    >
    > > > > > > > > CLIENT: loncmxs1024
    > > > > > > > > other calls: 2043
    > > > > > > > > other times (msec): avg 36095.581 min 27608.409 max 36212.573
    > > > > > > > ...
    > > > > > > > > Huge response times. So far this is the only way I can get real
    > > > > > > > > numbers out of the machine that show a problem!

    >
    > > > > > > > > Client rpc:
    > > > > > > > > Connection oriented
    > > > > > > > > calls badcalls badxids timeouts newcreds badverfs
    > > > > > > > > timers
    > > > > > > > > 510140 510107 0 510000 0 0

    >
    > > > > > > > You should really check for the timeout instead of the badcalls.
    > > > > > > > For trouble-shooting:

    >
    > > > > > > > 1) Client
    > > > > > > > a) Mount a localy exported Filesystem via NFS
    > > > > > > > - NFS is working at all or not
    > > > > > > > b) Mount the nfs export from the server via udp
    > > > > > > > - If it work check for network problems ( back hole - router , wrong
    > > > > > > > adpater settings )
    > > > > > > > c) Mount from a NFS server wihin the same subnet
    > > > > > > > d) Check the ethernet adapter for errors ( entstat )
    > > > > > > > e) Do a simple performance test between the server and the client
    > > > > > > > Server: ftp client
    > > > > > > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > > > > > > Client: ftp Server
    > > > > > > > put "| dd if=/dev/zero bs=32k count=1000" /dev/null

    >
    > > > > > > > f) Try to mount nfs share on the server from a differnet client within
    > > > > > > > the same subnet as the trouble causing client.

    >
    > > > > > > > 2) Server
    > > > > > > > a) Do step 1 also on the server ( I have seen that a server who was
    > > > > > > > able to serve the current connections but was unable to provide
    > > > > > > > service for new ones)

    >
    > > > > > > > hth
    > > > > > > > Hajo- Hide quoted text -

    >
    > > > > > > > - Show quoted text -

    >
    > > > > > > I was getting all wrapped up in the problem and forgetting to stand
    > > > > > > back and take it one step at a time ..

    >
    > > > > > > TCP mounts to locally exported filesystem fail with the same error.
    > > > > > > UDP mounts both to the local system and the remote server work fine.

    >
    > > > > > > I'm off to find out what can cause it, but if you have any
    > > > > > > pointers..

    >
    > > > > > > Thanks for your help

    >
    > > > > > > Matt.- Hide quoted text -

    >
    > > > > > > - Show quoted text -

    >
    > > > > > TCP mounts from other clients to the server work.

    >
    > > > > > Other problem clients have the same behaviour, some exist on different
    > > > > > networks. Working and Non-working clients can be found on the same
    > > > > > networks.

    >
    > > > > > all problem clients work with UDP but not TCP.

    >
    > > > > > entstat shows no errors, ftp tests run fine.

    >
    > > > > > matt- Hide quoted text -

    >
    > > > > > - Show quoted text -

    >
    > > > > While a failed TCP mount is in progress, this can bee seen on the
    > > > > server,

    >
    > > > > Proto Recv-Q Send-Q Local Address Foreign Address
    > > > > (state)
    > > > > tcp4 600032 343948 loncmxs1018.shilp loncmxs1008.34641
    > > > > ESTABLISHED

    >
    > > > > A huge Recv-Q and Send-Q, and it stays like that. The client appears
    > > > > hung with:
    > > > > NFS server loncmxs1018 not responding still trying

    >
    > > > Compare the output of the
    > > > "no -a" and "nfso -a" comannds and check as well with "lsattr -El
    > > > en0" the MTU size with a different and working aix 5.1 client

    >
    > > > hth
    > > > Hajo- Hide quoted text -

    >
    > > > - Show quoted text -

    >
    > > nfso options are the same, no differs by
    > > no=working client
    > > no2=failing client

    >
    > > [root@loncmxs1022] # diff no no2
    > > 2c2
    > > < thewall = 15852544
    > > ---> thewall = 13816832

    >
    > > 28c28
    > > < nbc_limit = 15590400
    > > ---> nbc_limit = 13554688

    >
    > > 32c32
    > > < nbc_pseg_limit = 16777184
    > > ---> nbc_pseg_limit = 14680032

    >
    > > 114a115

    >
    > > lsattr -El en0, ent0, et0 are all the same, except the failing client
    > > examined has 2 IP aliases set on en0.
    > > Other failing clients (there are 5 in total) do not have aliases
    > > applied.

    >
    > Then check if the portmapper has been started after nfsd and/or the /
    > etc/rpc is corrupted.
    >
    > A quick google search showes some procdure for NFS trouble shooting
    > likehttp://web.utanet.at/mario/exam/5129cb5.htm
    >
    > Check the procedure because i would do the same.
    > hth
    > Hajo- Hide quoted text -
    >
    > - Show quoted text -


    Hi, thanks very much for the help you have given. It's helped
    elucidate more info on the issue at least

    I had tried going through a few checklists before I came here,
    although that one looks a bit more thorough than any I found so I'll
    give it a try.

    I have been googling to try and find anyone with a similar problem
    where udp will work but tcp won't, and It's turning out fairly
    difficult to find that specifically. I _will_ fix it though. I will !


+ Reply to Thread