You are not logged in.
I'm not sure whether the annoyance I experience is a problem with Thunar, nfs, autofs, my nfs server or some other link in the chain ....
I am running a server based on Slackware 14.1, supporting nfs v3 service.
On my desktop client, running up-to-date ArchLinux, I mount the remote shares using autofs. The remote shares have the form /net/tower/mnt/diskN and /net/tower/mnt/user/A,,,A
In thunar I have /net/tower/mnt 'bookmarked'. If I open one of the shares (eg: mnt/user/Movies) I am unable to create/delete/rename any of the files/directories (the entries are 'greyed out' in the thunar File menu). However, if I go down a level into a subdirectory, I appear to have full write access. What is more confusing - if I then go back up a directory level to the original, non-writeable, directory, I am now able to write to it.
From terminal/console session I am able to modify entries (eg mv /net/mnt/user/Movies/a /net/mnt/user/Movies/b), while thunar is still not allowing me to make changes. The change made at the command line is promptly reflected in the thunar window.
Is anyone able to explain this behaviour and suggest what I can do to allow write on first time access to the directory.
Exports from the server take the form:
"/mnt/user/Movies" -async,no_subtree_check,fsid=100 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash)
The equivalent mount in Arch looks like:
tower:/mnt/user/Movies on /net/tower/mnt/user/Movies type nfs (rw,nosuid,nodev,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.22.0.100,mountvers=3,mountport=52483,mountproto=udp,local_lock=none,addr=172.22.0.100)
Offline
I opened a bug report about this issue a while ago and there has been no resolution as of yet.
Online
Thanks for pointing me to your report. Yes, the symptoms I experience are exactly the same as yours and I had elready discovered that an 'ls' from console averts the problem
Limited testing on Linux Mint indicates that nemo does not exhibit this behaviour, but thunar on Mint behaves the same as it does on Arch. This would suggest that the fault lies with thunar,
Offline