Word for Mac on NFS v4 share thinks documents are read only

[steinrr]

First of all: this is an issue I am having with Unraid as server - but I wanted to see if anyone using FreeNAS/TrueNAS has same experience. I guess it is similar NFS server that runs in background and that concepts are the same. I hope it is OK to ask for experiences from FreeNAS/TrueNAS regarding this topic - I guess it is a general issue.

I have a strange issue with server running NFS v4 shares.

Facts:
* Running a fresh install of Word on a fresh Mac
* Documents are on an NFS v4 network share
* The share and documents has all permissions: Read - Write - Execute (have not used any ACL)
* I can verify this by using "Get info" on a Word document and see that myselv, mygroup and all users has Read and Write. I can also verify directly on server. Documents are 777 (rwx for all)
* Ready only is not set on document
* Locked is not set on document

Symptoms:
* When I open a document located on the share in Word on the Mac - it displays a message that the document is read only and only gives me the option do duplicate it. I can duplicate it fine and save to the network location, but when opening the duplicated document, I get the read only message again.
* No other programs are behaving this way on the same share - Excel, Powerpoint etc works fine. I can even open a Word document in a text editor and are able to save it - so if it definitely not read only
* If I create a new Word document and saves it to this network share - I get the same behaviour - it gets read only
* If I map the network share using NFS v3 or Samba (SMB) protocol instead of NFS v4, it works fine - issue is only with NFS v4 (I prefer using NFS over SMB due to speed & reliability when there are many files)
So somehow Word thinks that documents on the network share are read only - while they definitely not are read only.

Any similar experiences with FreeNAS/TrueNAS or any ideas on what is the source of issue here?

 

[sretalla]

You might need to look into the options when mounting that NFS share... specifying "nolock"

Something like this:

Reddit - Dive into anything

www.reddit.com

You may be able to find similar advice for Mac somewhere, but I think that gives you the idea.

 

[steinrr]

You might need to look into the options when mounting that NFS share... specifying "nolock"

Something like this:

Reddit - Dive into anything

www.reddit.com

You may be able to find similar advice for Mac somewhere, but I think that gives you the idea.

Unfortunately there are no client mount options for NFS v4. These only works for previous versions of NFS.

 

[sretalla]

Unfortunately there are no client mount options for NFS v4. These only works for previous versions of NFS.

Are you trying to say that your Mac doesn't have the mount command?

What I was suggesting is not something that you would do on the TrueNAS end.

 

[steinrr]

Are you trying to say that your Mac doesn't have the mount command?

What I was suggesting is not something that you would do on the TrueNAS end.

No, I was a bit quick posting he reply and the forum did not give me an edit possibility.

The correct is that there are no mount options related to locking behaviour for NFS v4. Locking is totally rewritten in NFS v4 and cannot be controlled by mount options anymore. So these options are either not accepted or just plainly ignored.

 

[sretalla]

The correct is that there are no mount options related to locking behaviour for NFS v4. Locking is totally rewritten in NFS v4 and cannot be controlled by mount options anymore. So these options are either not accepted or just plainly ignored.

OK, so you tried it and it didn't work?

 

[steinrr]

OK, so you tried it and it didn't work?

Yes, I have tried "everything". Locking is not longer controlled from the client in NFS v4.

 

[sretalla]

I did some googling around and see what you mean...

It's strange as those options (nolock, local_lock) seem to be there in a manpage that specifically states it covers v4 and doesn't exclude those options in that case... but anyway (https://www.man7.org/linux/man-pages/man5/nfs.5.html in case you're curious).

 

[steinrr]

I did some googling around and see what you mean...

It's strange as those options (nolock, local_lock) seem to be there in a manpage that specifically states it covers v4 and doesn't exclude those options in that case... but anyway (https://www.man7.org/linux/man-pages/man5/nfs.5.html in case you're curious).

Yes, it is very undocumentet. Some of the options gives error when mounting and others are just ignored...

 

[sretalla]

I did come across this in my searching... are you sure you're mounting as nfsv4?

Set Default NFS v4 when connecting from Mac OS X Lion

I have installed an NFS File Server on Ubuntu 11.10, and that is working well. I am only able to connect to the NFS server from my Mac with this command: mount -t nfs -o vers=4 10.0.10.26:/srv ...

apple.stackexchange.com

 

[steinrr]

I did come across this in my searching... are you sure you're mounting as nfsv4?

Set Default NFS v4 when connecting from Mac OS X Lion

I have installed an NFS File Server on Ubuntu 11.10, and that is working well. I am only able to connect to the NFS server from my Mac with this command: mount -t nfs -o vers=4 10.0.10.26:/srv ...

apple.stackexchange.com

Yes, I am sure. I can examine the actual version after mounting. And also the fact that the Word issue is not an issue if I mount version 3 directly.