Since a few days, I’ve noticed a strange and abnormal behavior on my machine with Leap 15.4 as a NFS client. This behavior is new, although I did not change my configuration. Furthermore, I do not see this behavior on another Leap 15.4 machine, also acting as NFS client, and a priori configured the same way.
In an NFS share, if I create a file or a directory, it is not listed in the subsequent
ls, but it seems nevertheless to be created (also checked to be present on the NFS server’s physical media).
> mkdir test > echo "Test" > test.txt > ls (no mention of test or test.txt) > mkdir test mkdir: cannot create directory ‘test’: File exists
Also, if I move an existing file to a directory, the NFS client does not seem to track this move correctly (although it is correctly moved on the NFS server’s physical media).
> mv myfile.jpg directory/ > ls -l -????????? ? ? ? ? ? myfile.jpg > mv directory/myfile.jpg . (the file is correctly back)
Any idea what could be causing this?
Thanks & kind regards,
PS: If it helps, here is how the NFS share is mounted:
192.168.1.48:/media/RG on /media/RG type nfs4 (rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.46,local_lock=none,addr=192.168.1.48,_netdev)