Hi, I have been having issues when running MPICH2-1.4 on a NFSv4 filesystem (they both seem to work fine on their own). When I mount as NFS version 4, I get lots of NFS traffic on my internal network (seen when I run sudo iftop -i eth1) and the mpich2 tests time out or give i/o errors. However, when I mount the NFS as version 3, the MPICH2 tests seem to work without any major problems. Even though I can get this working by switching to NFSv3, I would like to get MPICH2 working with NFSv4, if possible. Is there something in my NFS configuration (see below) that is not possible with NFSv4 or is this some sort of conflict between MPICH2-1.4 and NFSv4? Thanks, Greg Here is the /etc/exports on the NFS server: /usr/local 192.168.2.0/24(async,fsid=1,ro,no_root_squash,no_subtree_check) /home 192.168.2.0/24(async,fsid=2,rw,no_root_squash,no_subtree_check) Here are the NFS mounting details from "nfsstat -m": NFSv4 (hangs and times out, with large quantity of NFS traffic): /home from 192.168.2.11:/home/ Flags: rw,relatime,vers=4,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,port=0,timeo=20,retrans=32,sec=sys,clientaddr=192.168.2.1,minorversion=0,local_lock=none,addr=192.168.2.11 /usr/local from 192.168.2.11:/usr/local/ Flags: ro,relatime,vers=4,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,port=0,timeo=20,retrans=32,sec=sys,clientaddr=192.168.2.1,minorversion=0,local_lock=none,addr=192.168.2.11 NFSv3 (works; mounted in fstab same as above except with nfs replacing nfs4 and nfsv and an extra option nfsvers=3): /home from 192.168.2.11:/home Flags: rw,relatime,vers=3,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=20,retrans=32,sec=sys,mountaddr=192.168.2.11,mountvers=3,mountport=55359,mountproto=udp,local_lock=none,addr=192.168.2.11 /usr/local from 192.168.2.11:/usr/local Flags: ro,relatime,vers=3,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=20,retrans=32,sec=sys,mountaddr=192.168.2.11,mountvers=3,mountport=55359,mountproto=udp,local_lock=none,addr=192.168.2.11 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html