On the original question, you need to specify the fsid for the file system. Otherwise you get an fsid that's derived in part from the device numbers, so different device numbers on the failover leads to a different fsid. wrt NFS over UDP, it isn't supported with NFSv4, and will lead to random hangs. At least for us, NFSv4 is a big enough win that we gave up NFS over UDP. -dan > On Feb 13, 2015, at 12:16, emmanuel segura <emi2fast@xxxxxxxxx> wrote: > > I had the same problem with nfs ha with rhcs, i solved using udp when > i mounted the shares in client side. > > 2015-02-13 17:39 GMT+01:00 Equipe R&S Netplus <netplus.root@xxxxxxxxx>: >> Hello, >> >> I would like to setup a cluster of NFS. >> With RHCS, I use the ressource agent "nfsserver". >> >> But I have a question : >> Is it possible manage a NFS server where NFS client "will not be aware of >> any loss of service" ? In other words, if the NFS service failover the NFS >> client don't see any change. >> >> Actually when there is a failover, I can't access to the NFS server anymore. >> Indeed, I had the message "Stale NFS file handle". >> In client NFS log : >> << >> NFS: server X.X.X.X error: fileid changed >>>> >> >> Is there any solution please ? >> Thank you. >> >> >> -- >> Linux-cluster mailing list >> Linux-cluster@xxxxxxxxxx >> https://www.redhat.com/mailman/listinfo/linux-cluster > > > > -- > esta es mi vida e me la vivo hasta que dios quiera > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
