Hello, I'm having a problem that I think is related to autofs; I apologize in advance if it isn't. I have a cluster with two partitions, /home/cw and /misc_data, that are automounted to all nodes in the cluster. There is a symbolic link, /home/cw/DATA3D, that points to /misc_data/cw/DATA3D. Most of the time this link works without a problem. When I run code that writes to /home/cw/DATA3D, however, it crashes, complaining that there is no such file or directory. If I log in to the node and ls -l /misc_data_cw, it gives me a flashing red name for DATA3D as if it is a broken link, even though the rest of the partition is mounted and acting normally. Furthermore, I can avoid the whole problem by logging in to the node before the job runs and entering /misc_data/cw/DATA3D. We didn't have this problem when we were running RedHat 3.3; it's only since we upgraded to 4.0 (with autofs-4.1.3-155) that this has shown up.
Any advice is appreciated. Many thanks, Chris _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
