I'm having some issues using NFS to access files on a small PC via a home LAN.
It appears to work perfectly when I'm using Nautilus or the command line, but when I try to save an application such as LibreOffice or GIMP, I get a few second delay, then a "Write error". When opening an existing file from the NFS share it tells me "This file is locked for editing by Unknown User".
These applications can open and save files on local drives without problems.
My current workaround is to open as Read-only and save the file onto my desktop, then use Nautilus to copy it to the location from where I originally opened it.
My local PC is using Ubuntu 20.04, and the server says it's on: "5.3.0-53-generic #47~18.04.1-Ubuntu SMP"
My local /etc/fstab entry:
192.168.50.186:/nas/shared /shared nfs rsize=8192,wsize=8192,timeo=14,hard,nfsvers=3
On the server my /etc/exports file:
/nas/shared 192.168.50.186/255.255.255.0(rw,insecure,no_subtree_check,async)
In 18.04 this problem only affected LibreOffice, but now it also affects the GIMP and Krita and probably others.
I finally worked out what the issue is - group permissions.
The files on the NAS server all have R/W/X permissions for a group called "nasusers" with id=1002.
This can be seen with a simple
ls -la
in the folder on the server.Doing the same command locally shows the group as "1002" because the group "nasusers" does not exist on the local client machine. To fix this I ran (locally on my client):
Running
id
shows that my user is not a member of this group. To add myself to the group I ran (locally on my client):Also, on the server I set the permissions of the shared files to 770, so owner and group have full permissions and others have none.
This has allowed me to open and save files from the NAS server from LibreOffice and the GIMP without errors.
based on the link(and the testing you've done so far), add another mount to a subdirectory of your share from your home directory and test with libreoffice.
(you can change the current mount but, I'm trying not to be too invasive of your current setup)
I think you may have to use subtree_check