https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-and-nfs/m-p/2752729#M714006 Thanks for your questions:<BR /><BR />1) Filesystems are being mounted using automounter.<BR />2) Using the native NFS nsf.server and nfs.client not the SG NFS.<BR />3) fuser being used to kill processes using the mount points.<BR />4) I don't believe pkg.cntl has duplicate entries.<BR />5) App server are mounting using automounter as well.<BR />6) Apps point to the cluster's hostname and IP. (i.e. hostname goes away once package goes down).<BR /> Wed, 26 Jun 2002 19:44:12 GMT Tony Romero 2002-06-26T19:44:12Z https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-and-nfs/m-p/2752726#M714003 When I failover from host1 to host2 one of the many NFS filesystems does not unmoun, which causes the package to fail when it tries to come up on host2. Any ideas or familiarity with this type of problem.<BR /><BR />The landscape is as follows:<BR /><BR />host1 - prod db server<BR />host2 - qa db server (failover server)<BR />app1 - app server host<BR />app2 - app server host<BR />app3 - app server host<BR /><BR />The NFS mount point on the app# servers becomes stale, which also prevents the app from coming up. However when the nfs.server and nfs.client is stopped or servers rebooted everything works well again.<BR /><BR />Thanks... Wed, 26 Jun 2002 16:42:28 GMT https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-and-nfs/m-p/2752726#M714003 Tony Romero 2002-06-26T16:42:28Z https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-and-nfs/m-p/2752727#M714004 I have a few questions to ask that may clear up your issue..<BR /><BR />1. Is the filesystem to be unounted in /etc/exports ? It shouldn't be ...<BR />2. Are you using the current NFS Toolkit for MC/SG ? <BR />3. In the pkg.cntl script does the unmount_fs function include a 'fuser -ck /mount_point' ? It should ...<BR />4. The mount point isn't listed twice is it (in the pkg.cntl) ?<BR />5. What type of mount are you using from app# server, hard or soft ? probably should be soft ...<BR /><BR />Good Luck! Wed, 26 Jun 2002 16:58:10 GMT https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-and-nfs/m-p/2752727#M714004 Robert Gamble 2002-06-26T16:58:10Z https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-and-nfs/m-p/2752728#M714005 Tony, <BR /><BR />I just thought of one other question.<BR /><BR />Are the app# servers pointing to the package name / IP address and not the cluster node that is down ? They should be pointing to the package name / IP of the package, not the hostname or IP of the server.<BR /><BR />Good Luck! Wed, 26 Jun 2002 17:42:34 GMT https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-and-nfs/m-p/2752728#M714005 Robert Gamble 2002-06-26T17:42:34Z https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-and-nfs/m-p/2752729#M714006 Thanks for your questions:<BR /><BR />1) Filesystems are being mounted using automounter.<BR />2) Using the native NFS nsf.server and nfs.client not the SG NFS.<BR />3) fuser being used to kill processes using the mount points.<BR />4) I don't believe pkg.cntl has duplicate entries.<BR />5) App server are mounting using automounter as well.<BR />6) Apps point to the cluster's hostname and IP. (i.e. hostname goes away once package goes down).<BR /> Wed, 26 Jun 2002 19:44:12 GMT https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-and-nfs/m-p/2752729#M714006 Tony Romero 2002-06-26T19:44:12Z