From: Peter.Stern@weizmann.ac.il
Date: Mon May 20 2002 - 10:35:45 EDT
My original message is below.
Thanks to Selden Ball and Dr. Thomas Blinn. The problem is complicated
because the interaction of the NFS server and client is complex, but
from the very useful comments I got from Tom, it appears that anytime
after a server reboot until the client is also rebooted, there is a
possibility that the client will try to access files that for one reason
or another are no longer valid in the context of the client. For
example, the client may have been accessing a file on the server when it
rebooted.
In any case, unless I want to reboot all my clients every time that I
need to reboot the server (which is infrequent), I will have to live
with this. It doesn't seem to be a major problem.
> I periodically find the following messages in /var/adm/messages on my
> my ES40 (v4.0f pk #7):
>
> May 15 21:46:28 server00 vmunix: NFS server: fs(4095,576265) not
> mounted, RFS3_GETATTR, client address = 132.xx.yy.15
> May 15 22:00:58 server00 vmunix: NFS server: fs(4095,576265) not
> mounted, RFS3_GETATTR, client address = 132.xx.yy.17
> May 15 22:11:07 server00 vmunix: NFS server: fs(4095,576265) not
> mounted, RFS3_GETATTR, client address = 132.xx.yy.48
> May 15 22:21:54 server00 vmunix: NFS server: fs(4095,576265) not
> mounted, RFS3_GETATTR, client address = 132.xx.yy.48
>
> What do they mean and what causes them? Are they anything to worry
> about?
>
>
Regards,
Peter
Peter Stern
Chemical Physics Department
Weizmann Institute of Science
76100 Rehovot, ISRAEL
email: Peter.Stern@weizmann.ac.il
phone: 972-8-9342096
fax: 972-8-9344123
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:42 EDT