Suddenly can't write to nfs share anymore

Server LEAP 15.3:

:~> cat /etc/exports | grep Publico
/home/blimmer/Torrents/Gravados/Publico *(rw,root_squash,sync,no_subtree_check)
:~>

Client LEAP 15.2:

:~> cat /etc/fstab | grep Publico
192.168.0.3:/home/blimmer/Torrents/Gravados/Publico  /home/blimmer/Shares/Publico\040Compartilhado  nfs    soft,noauto,rw,users,timeo=100,retrans=200  0  0
:~>

Users are identical in both machines - same name, password, UID/GID and groups.

Last time I tried I had write access to Publico, now I can only read/copy, can’t write/delete files. Maybe this happened after upgrading the server from 15.2 to 15.3, I don’t recall.

Mount folder permissions on client are:

:~/Torrents/Gravados> ls -la | grep Publico
drwxrwxrwx   9 blimmer users  4096 jul  1 12:25 Publico
:~/Torrents/Gravados>

Any idea about what happened?

Thanks,

Bruno

Just checked another client running LEAP 15.3 and the same problem happens.

And server folder permissions are:

:~/Torrents/Gravados> ls -la | grep Publico
drwxrwxrwx   8 blimmer users   286 jul 15 09:33 Publico
:~/Torrents/Gravados> 

P.S.: I use Dolphin (KDE) to access the share.

Show output of

grep Publico /proc/self/mountinfo

on client.

And did you check (with e.g. mount) if the NFS file system is mounted read-only (by incident)?

Good suggestion, thanks. It is rw:

:~> mount | grep Publico
192.168.0.3:/home/blimmer/Torrents/Gravados/Publico on /home/blimmer/Shares/Publico Compartilhado type nfs4 (**rw**,nosuid,nodev,noexec,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=100,retrans=200,sec=sys,clientaddr=192.168.0.13,local_lock=none,addr=192.168.0.3) 
:~>

Thanks, arvidjaar.

:~> grep Publico /proc/self/mountinfo
257 142 0:63 / /home/blimmer/Shares/Publico\040Compartilhado **rw**,nosuid,nodev,noexec,relatime shared:97 - nfs4 192.168.0.3:/home/blimmer/Torrents/Gravados/Publico **rw**,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=100,retrans=200,sec=sys,clientaddr=192.168.0.13,local_lock=none,addr=192.168.0.3 
:~> 

Seems OK, similar to the mount output.

NFSv4 needs extra configuration to treat users as identical. Does it work with NFSv3 (vers=3 mount option)?

I think you nailed it!

Both os Yast NFS server and NFS client modules have an option to enable nfsv4 and if I uncheck the server “enable nfsv4” option, I **can’t **mount the share in the client anymore. But if I uncheck the client option too I can access the share with write permissions.

Do you recommend staying with NFSv3 or should I try to use v4? I didn’t test mounting with ver3 option as it is working now.

I also have to check if this will impact a firetv stick that access other ro shares.

Thanks a lot!

No problem there, as expected.

I do not see any compelling reason to use NFSv4 in your case.

Same here. I have never switched on NFS-4. And it works like it did for ~35 years.

OK, thank you. I’ll stay with v3.