David.Mackintosh@xdroop.com wrote:
Anyone seen this before?
I have a number of file systems nfs mounted onto clients running various versions of CentOS (and Upstream), although mostly they are v5.x flavors. =20
The server is a Network Appliance filer.
When the build process for this team runs, it sometimes dies because it can't find files in the automounter tree; if the engineer checks, he sometimes sees a problem, and sometimes doesn't; for example:
[pdbuild@build-c5u1: ~] ll /tools/vault/kernels ls: /tools/vault/kernels: No such file or directory [pdbuild@build-c5u1: ~] ll /tools/vault/kernels total 152K drwxr-xr-x 4 pdbuild everyone 4.0K Aug 7 2007 2.4.21-40.EL.CUSTOM.01smp/ ... drwxr-xr-x 7 pdbuild everyone 4.0K Oct 16 2007 2.6.18-xen/ [pdbuild@build-c5u1: ~] df /tools/vault/kernels Filesystem Size Used Avail Use% Mounted on nas02:/vol/tools/vault 779G 655G 124G 85% /tools/vault
Now I've seen this before where some processes don't wait for the automounter to do its thing before continuing; they just report "fail" and move on to the failure handling.
What sort of map is being used for this mount point? i.e. what is the contents of your /etc/auto.master ?
James Pearson