Could not edit Microsoft Office files from mountpoint about go-nfs HOT 6 OPEN

@willscott
I've tried to mount with options locallocks, and it looks better.
But there are still some problems.
Word docx(doc) files could be saved with some wired temporary directories like abc.docx.sb-xxxxxx-xxxxx
Excel xlsx(xls) files could be saved without any sb temporary directory
PowerPoint pptx(ppt) files could be created but couldn't be saved.

• NFS Server: macOS, sudo ./example/osnfs /path/to/files/ 45678
• NFS Client: macOS, sudo mount_nfs -vvv -o port=45678,mountport=45678,proto=tcp,nosuid,sync,locallocks "localhost:/nfs" /path/to/mount

from go-nfs.

I wonder if #72 was the underlying issue behind this

can you try again with the current version?

from go-nfs.

@willscott
Same...

from go-nfs.

Does anyone have a clear idea what is happening here? This is affecting rclone users in rclone/rclone#7973 in exactly the same way.

Putting nolock or locallocks doesn't fix the problem though - the symptoms are as described above #54 (comment)

Is this a problem because the nfs server doesn't implement locking? If so could we implement a skeleton locking system?

I notice that memfs has a stubbed out Lock and Unlock which don't appear to be called anywhere

from go-nfs.

@ncw - the reason memfs does not implement lock / unlock is because the accompanying 'Network Lock Manager (NLM)
protocol' is not implemented here. The protocol is documented in RFC 1813 - but it will be a bigger effort than the method you point to.

from go-nfs.

Thanks @willscott

What do you think the best way forward with this issue is? Rclone can't support locking so how can we tell the clients not to try?

from go-nfs.