From: Scott Taylor <scottt@methodstudios.com>
To: nfs@lists.sourceforge.net
Subject: WARNING: rfs3call
Date: Mon, 15 Aug 2005 18:03:53 -0700 [thread overview]
Message-ID: <43013B79.2070800@methodstudios.com> (raw)
Hi.
In an environment with a Fedora3 (2.6.11.3 kernel) serving NFS to
several IRIX (6.5.21) boxen, I occasionally see the following messages
in the IRIX system's syslogs:
Aug 15 16:03:42 4A:K6 unix: WARNING: rfs3call: file temporarily
unavailable on the server s2, retrying...
Aug 15 17:44:48 4A:K6 unix: WARNING: rfs3call: file temporarily
unavailable on the server s2, retrying...
Aug 15 17:46:07 4A:K6 unix: WARNING: rfs3call: file temporarily
unavailable on the server s2, retrying...
Some of the IRIX boxen weather these messages well, while others (onyx2
and octane1) will hang for a while.
All of these systems reside on the same gigabit ethernet switch.
The line in the IRIX boxen fstab looks like this :
s2:/array /ocean nfs rw,soft,bg,rsize=32768,wsize=32768,proto=tcp 0 0
Things seemed to be working nicely for a long time, and I cannot
identify any specific change to the network or machines that may have
led to these messages.
Many thanks for any thoughts or input - please reply to my email address
directly as I do not subscribe to the list.
Thanks,
Scott
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2005-08-16 1:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43013B79.2070800@methodstudios.com \
--to=scottt@methodstudios.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox