Hello,
Any indications of exactly what this error means?
rpc-srv/tcp: nfsd: sent only -107 bytes of #### - shutting down socket error
They are receiving the error in the range of 10-30 times per second on the
heavily used nfs servers.
This is running with nfs over tcp, with 32k packet sizes, what 4 nfs servers
and roughly 230 clients. Until the amount of nfs usage increased this error
did not appear to be happening, or was not noticed.
The clients are also getting these messages:
RPC: tcp_data_ready socket info not found!
/proc/mounts confirms the 32k read/write, and that tcp is being used.
There are some other odd things happening, the admins and users indicate
that
they have had several instances of editing an existing file and then saving
the file and that file not being there after they exit and save in the
editor, and not sure if this is a related problem or something else
entirely.
Roger
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Mon, Sep 20, 2004 at 11:41:34AM -0500, Roger Heflin wrote:
> Any indications of exactly what this error means?
>
> rpc-srv/tcp: nfsd: sent only -107 bytes of #### - shutting down socket error
It means nfsd got an ENOTCONN from sendto(). You want to increase the
number of nfsds; these messages should mostly go away then.
Olaf
>
> They are receiving the error in the range of 10-30 times per second on the
> heavily used nfs servers.
>
> This is running with nfs over tcp, with 32k packet sizes, what 4 nfs servers
> and roughly 230 clients. Until the amount of nfs usage increased this error
> did not appear to be happening, or was not noticed.
>
> The clients are also getting these messages:
> RPC: tcp_data_ready socket info not found!
>
> /proc/mounts confirms the 32k read/write, and that tcp is being used.
>
> There are some other odd things happening, the admins and users indicate
> that
> they have had several instances of editing an existing file and then saving
> the file and that file not being there after they exit and save in the
> editor, and not sure if this is a related problem or something else
> entirely.
>
> Roger
>
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> NFS maillist - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
--
Olaf Kirch | The Hardware Gods hate me.
[email protected] |
---------------+
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs