Hello Scott:
The key here is that you switched to NFSv4. Previously versions of NFS were connectionless. This was seen as a good thing because it meant that if the server had what you called "an event" or the network had a glitch, it wasn't visible to the client unless the server didn't come back.
NFSv4 works more like CIFS and uses a connection. That is why you are seeing all the issues. You might want to go back to version 3 unless you can use the new features of v4 such as parallel NFS. Most applications are not taking advantage of those new features.
--April
Sent from my iPad
On May 29, 2013, at 7:27 AM, Scott Eno s.eno@me.com wrote:
Hi,
I used to not see any issue with nfs mounts during cf events. When we went to RHEL 6 with NFSv4 as the default, then unix hosts started having all sorts of stale mount issues during cf events. Anything still using NFSv3 (VMware, oracle) is still very forgiving.
Scott Eno s.eno@me.com
On May 29, 2013, at 3:07 AM, Rafał Radecki radecki.rafal@gmail.com wrote:
Hi All.
I have two FAS3210 in 7-mode Actvie/Active. I perform takeover/gieback and see that the outage is visible for clients for nfs mounts. From your experiences should it be so? I think that information about nfs sessions and IP address are moved to the takeover node so in theory it should not be visible.
Best regards, Rafal. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters