Description of problem: I'm using autofs to bind mount directories from AFS to mount points under /ncsu. When autofs first mounts a mount point the command that triggers it returns No such file or directory but the mount is mounted correctly. $ ls /ncsu/sfcallic ls: /ncsu/sfcallic: No such file or directory $ ls /ncsu sfcallic $ ls /ncsu/sfcallic <directory listing> I have the following map defined: /ncsu ldap://ldap.ncsu.edu/nisMapName=auto_ncsu,ou=mounts,dc=ncsu,dc=edu --timeout=180 --debug This mostly affects a script that is used to os.stat() a directory under /ncsu to verify it is a valid "locker" and then run a .environment script in that locker to set up the environment for the contained application. Version-Release number of selected component (if applicable): autofs-5.0.1-0.rc2.55 How reproducible: Oddly. It seems to most frequently happen at the console of the machine in question. Less so if you are ssh'd into the machine.
Created attachment 273221 [details] syslog from autofs This contains some logs from autofs with --debug. I don't see a specific problem it says its able to mount the directory and this was from an instance where ls /ncsu/sfcallic returned no such file or directory.
This doesn't seem to affect root, just normal users. I can confirm the behavior with autofs-5.0.1-0.rc2.42.i386.rpm, autofs-5.0.1-0.rc2.55.i386.rpm, and autofs-5.0.1-0.rc2.43.0.2.i386.rpm
*** This bug has been marked as a duplicate of 371341 ***