sthaug@nethelp.no writes:
We have an F330 which normally functions as a News spool (and works very well, btw). Today I tried storing a large (1.5 GByte) file on the NetApp, and a while later (a few hours) tried to delete the same file. During the delete, I got *lots* of
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
in the log. As soon as the delete was finished, everything was back to normal again.
The NetApp runs 3.1.5 (3.1.5d, I believe), and is connected to the NFS client machine (snipp) via a dedicated 100TX Ethernet. The NFS client machine is an Ultrasparc running Solaris 2.5.1.
Anybody seen this before?
Yes. This is fixed in 3.1.6, if memory serves me.
On 1 Aug 1997, Ketil Kirkerud Elgethun wrote:
sthaug@nethelp.no writes:
The NetApp runs 3.1.5 (3.1.5d, I believe), and is connected to the NFS client machine (snipp) via a dedicated 100TX Ethernet. The NFS client machine is an Ultrasparc running Solaris 2.5.1.
Yes. This is fixed in 3.1.6, if memory serves me.
Hrm... I was seeing similar behaviour when I had my news history file on an F220 running 4.0.1c (NFS only). INN would report various I/O errors and RPC timeouts when it tried to unlink the old history file and replace it with the new history.n file. Moving the history to a second local disk solved that problem.
-
Brian Tao -
Ketil Kirkerud Elgethun