From owner-freebsd-stable@FreeBSD.ORG Fri Jun 29 09:45:28 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AE0E106564A for ; Fri, 29 Jun 2012 09:45:28 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 4F3CE8FC15 for ; Fri, 29 Jun 2012 09:45:28 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1SkXlW-0006GN-N1; Fri, 29 Jun 2012 12:45:26 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: freebsd-stable@freebsd.org, danny@cs.huji.ac.il In-reply-to: References: Comments: In-reply-to Daniel Braniss message dated "Fri, 29 Jun 2012 11:37:18 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 Jun 2012 12:45:26 +0300 From: Daniel Braniss Message-ID: Cc: Subject: Re: nfs problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2012 09:45:28 -0000 > Hi, > starting about last week, I'm getting: > > rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken > pipe (32) > rsync: write failed on "/net/rnd/dist/tmp/local/amd64.FreeBSD_8.3-wip/compat/li > nux/usr/lib/locale/locale-archive.tmpl": Permission denied (13) > rsync error: error in file IO (code 11) at receiver.c(322) [receiver=3.0.9] > rsync: connection unexpectedly closed (21872 bytes received so far) [sender] > rsync error: error in rsync protocol data stream (code 12) at io.c(605) > [sender=3.0.9] > > the server is running 8.2, but the client is very upto date, 8.3-stable as of > this morning > (local time). > > after runing rsync several times, it finaly gets synced. > > another item is that i'm using am-utils, but I don't see it causing the problem > > I will try using tcp (instead of udp) soon. > > any insights? > > cheers, > danny the problem is most probably NFS/UDP related. I took am-utils out of the equation. mounted using TCP, and no problems mounted using UDP: Jun 29 12:38:14 pe-02 kernel: nfs server nrnfdn:sf/s ds isseterr:vve ernr o trrnn dd:r:e/s/pddoinisdsitt::n nngoo Jun 29 12:38:14 pe-02 kernel: tt Jun 29 12:38:14 pe-02 kernel: Jun 29 12:38:14 pe-02 kernel: <<66>> rreessppoonnddiinngg Jun 29 12:38:14 pe-02 kernel: Jun 29 12:38:14 pe-02 kernel: nfs server rnd:/dist: not responding Jun 29 12:38:14 pe-02 last message repeated 11 times Jun 29 12:38:27 pe-02 kernel: nfs server rnd:/dist: is alive again the above happens about every 15 seconds (you have to learn to read in between the bytes :-) cheers, danny