We see a similar message all the time:
Aug 3 08:53:21 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Aug 3 08:53:29 tofu kernel: nfs server netapp1.alt.net:/home: not responding Aug 3 08:53:29 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Aug 3 08:53:30 tofu kernel: nfs server netapp1.alt.net:/home: not responding Aug 3 08:53:30 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Aug 3 08:53:42 tofu kernel: nfs server netapp1.alt.net:/home: not responding Aug 3 08:53:42 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Aug 3 08:54:03 tofu kernel: nfs server netapp1.alt.net:/home: not responding Aug 3 08:54:03 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Aug 3 08:54:08 tofu kernel: nfs server netapp1.alt.net:/home: not responding Aug 3 08:54:09 tofu kernel: nfs server netapp1.alt.net:/home: is alive again
Note, the frequency!
This is when mostly reading/accessing files with occasional writes. This happens with NFS v2 and v3. Is there a way to determine whether this is a bug with our client OS (BSD/OS 3.0) or the NetApp?
Chris
Aug 1 15:37:22 snipp unix: NFS server snapp not responding still trying Aug 1 15:37:22 snipp unix: NFS server snapp ok