David.Mackintosh at 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 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 Any errors in syslog ? At my company we run automunter as well mostly on CentOS 4.x, and RHEL 4.x, though some newer systems are on 5.x. The only time I get that kind of error is if a firewall is blocking the connections, and there is always an error in syslog saying that it couldn't connect to the NAS. e.g. Jan 22 02:52:24 pd1-cas01 automount[32591]: >> mount: mount to NFS server 'exnas' failed: timed out (giving up). Jan 22 02:58:42 pd1-cas01 automount[23530]: >> mount: backgrounding "exnas:/exavol/system_logs/syslogs" How many systems do you have mounting the NetApp? Here we are migrating from a BlueArc based system to an Exanet based system, NetApp's architecture limits it's performance too much for our needs(and price point). Maybe with OnTap 8.0 with the integration of GX stuff it will be better. nate