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 at build-c5u1: ~] ll /tools/vault/kernels ls: /tools/vault/kernels: No such file or directory [pdbuild at 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 Jun 26 2007 2.6.16.33-1-xen/ drwxr-xr-x 7 pdbuild everyone 4.0K Aug 7 2007 2.6.16.33-xen/ drwxr-xr-x 4 pdbuild everyone 4.0K Jan 3 2008 2.6.18-53.1.4.el5/ drwxr-xr-x 4 pdbuild everyone 4.0K Feb 11 2008 2.6.18-53.1.6.el5/ drwxr-xr-x 4 pdbuild everyone 4.0K Nov 15 2007 2.6.18-53.el5/ drwxr-xr-x 4 pdbuild everyone 4.0K Sep 24 2007 2.6.18-8.el5/ drwxr-xr-x 7 pdbuild everyone 4.0K Oct 16 2007 2.6.18-xen/ [pdbuild at 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 automount= er to do its thing before continuing; they just report "fail" and move on to the failure handling. I'm guessing that I need some magic on the automounter configuration to change this behavior, can anyone point me in the right direction? Thanks for your time. -- /\oo/\ / /()\ \ David Mackintosh | dave at xdroop.com | http://www.xdroop.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20090201/52572ff4/attachment-0004.sig>