When I mounted our NFS datastores on our vSphere hosts I used NFS 3.

Now Im being bitten by this bugfeature which was causing this issue when trialling Veeam Reading I dont see any obvious issue with using NFS 4.1.

We dont use Storage IO control, Storage DRS or SRM.

As simple as unmount and remount but using 4.1 Im on 6.7 U1 and right now I feel dumb.

Rich 5 comments share save hide report 100 Upvoted This thread is archived New comments cannot be posted and votes cannot be cast Sort by best.

When we used nfs on our FAS we ran 5.5 and had to work around that bug.

Share Report Save level 1 2 years ago I believe you dont want NFS 3 and NFS v4,1 used at the same time, as they use different locking mechanisms.

Share Report Save level 2 1 year ago Yeah never mount the same data store with different versions.

Bad things will happen 1 Share Report Save level 1 2 years ago Just wanted to say that Veeams proprietary NFS client supports both versions 3 and 4.1, so this part should not be a consideration either.

Share Report Save level 2 Original Poster 2 years ago Yeah I saw that but I dont know how set I am on Veeam as we use Commvault for other data.

If there is no downside in using 4.1 that seems the right answer so I should flip to that asap before I move any more VMs across.

Read the rules before posting.

Members 579 Online Created Oct 7, 2008 Join Top posts march 1st 2019 Top posts of march, 2019 Top posts 2019 help Reddit App Reddit coins Reddit premium Reddit gifts about careers press advertise blog Terms Content policy Privacy policy Mod policy Reddit Inc 2021.

Nfs 3 Vs 4.1