> On 29/06/2012 10:45, Daniel Braniss wrote: > >> 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 > > > Its also possible you are hitting a bug I came across recently. > See http://lists.freebsd.org/pipermail/freebsd-current/2012-June/034860.html > basicly mountd may give incorrect permission denied errors when it is > refreshing the exports list due to non-atomic operations. > see > > kern/131342 > kern/136865 Hi Vince, I thought so too, there used to be a bug caused by am-utils umounting, succeding even if the mount was active, then re-mounting, which caused all kind of problems, the work around was to increase the timeout. But I don't think it's the case here, unless mountd has a life of its own. Furthermore, rsync works without a glitch when mounted nfs/tcp. thanks, danny
_______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
