Re: nfs send error 32
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 AndersonSr. Systems AdministratorCentaur Technology A lost ounce of gold may be found, a lost moment of time never. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nfs send error 32
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. Thanks Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NetApp and 'nfs send error 32'
On Thu, Jul 10, 2003 at 10:12:36AM +0300, Danny Braniss wrote: > hi all, > googling shows this not to be anything new, but ... > it happend when we enabled tcp/nfs on our NetApp fileservers. > so the question is: > 1- is it serious - it doesn't seem so ... > 2- can it be ignored? > > the main problem is that to turn it off, i have to reboot some 600 machines :-( This is nothing more then a lost TCP connect. Connection is reestablished and commands are retransfered. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NetApp and 'nfs send error 32'
hi all, googling shows this not to be anything new, but ... it happend when we enabled tcp/nfs on our NetApp fileservers. so the question is: 1- is it serious - it doesn't seem so ... 2- can it be ignored? the main problem is that to turn it off, i have to reboot some 600 machines :-( thanks, danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
