From: Danny Smith <dannys@cinesite.co.uk>
To: nfs <nfs@lists.sourceforge.net>
Cc: Iain Irwin-Powell <Iain@cinesite.co.uk>
Subject: Re: NFSERR_EAGAIN - resolved.
Date: Wed, 16 Jul 2003 16:53:47 +0100 [thread overview]
Message-ID: <3F15750B.9080302@cinesite.co.uk> (raw)
In-Reply-To: <3F0DB088.303@cinesite.co.uk>
Danny Smith wrote:
> I've been trying to resolve some issues we have with a set of systems
> running 2.4.20+NFS_ALL, dual CPU and Gigabit Ethernet. They're talking
> to SGI IRIX servers, (6.5.19), and having intermittent problems - this
> can be seen sometimes where an NFS mounted directory will "disappear",
> but subsequently be accessible. No errors are returned to the shell -
> the directory just appears to have no entries.
>
> This seems (although I don't have proof positive yet, more testing is
> in progrees) to coincide with errors in the logs:
>
> Jul 9 14:18:09 trout-node13 kernel: nfs_stat_to_errno: bad nfs status
> return value: 11
>
I've found the cause of these messages - SGI are in the clear - it's not
coming from their servers.
It's 'amd' (am-utils) which is providing the incorrect responses.
Trigger seems to be trying to access an automount on a host which is not
running an NFS server. amd then sends back a garbled response over the
loopback interface (after getting several "RPC - program not registered"
responses).
Whether this is causing our other problems remains to be seen.
Danny
--
Danny Smith
Senior Systems Administrator, Cinesite (Europe) Ltd
020 7973 4000 - x4055 / dannys@cinesite.co.uk
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-07-16 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 18:29 NFSERR_EAGAIN Danny Smith
2003-07-10 22:41 ` NFSERR_EAGAIN Trond Myklebust
2003-07-11 9:55 ` NFSERR_EAGAIN Danny Smith
2003-07-11 10:13 ` NFSERR_EAGAIN Trond Myklebust
2003-07-16 15:53 ` Danny Smith [this message]
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=3F15750B.9080302@cinesite.co.uk \
--to=dannys@cinesite.co.uk \
--cc=Iain@cinesite.co.uk \
--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