Date: Tue, 17 May 2005 06:35:31 -0500 From: Eric Anderson <anderson@centtech.com> To: Konrad Heuer <kheuer2@gwdg.de> Cc: freebsd-questions@freebsd.org Subject: Re: nfs send error 32 Message-ID: <4289D703.1030604@centtech.com> In-Reply-To: <20050517130356.C99328@gwdu60.gwdg.de> References: <20050517130356.C99328@gwdu60.gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Konrad Heuer wrote:
> Hi all,
>
> I've an NFS-mounted filesystem (server runs deadrat linux) on a lot of my
> FreeBSD systems (4.11R), mount options are
> "bg,rw,intr,-T,-r32768,-w32768". Using TCP and 32k buffers does enhance
> performance notably.
>
> But I've a couple of error messages in /var/log/messages of my clients
> each day like:
>
> date client /kernel: nfs send error 32 for server deadrat:/fs
>
> When looking into /usr/src/sys/nfs/nfsproto.h, I don't find anything about
> error code 32.
>
> Any idea or explanation would be very very welcome!
>
> BTW: NFS server has to run deadrat linux, and more nfs file systems have
> to be mounted in future from the same or similar machines.
I think it's a lost TCP connection. From man errno:
32 EPIPE Broken pipe. A write on a pipe, socket or FIFO for which
there is no process to read the data.
Not sure why the connection is dropping, but there could be a whole slew
of reasons for that.
Eric
--
------------------------------------------------------------------------
Eric Anderson Sr. Systems Administrator Centaur Technology
A lost ounce of gold may be found, a lost moment of time never.
------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4289D703.1030604>