Date: Wed, 28 Mar 2007 15:11:07 +0200 From: "Ulrich Spoerlein" <uspoerlein@gmail.com> To: freebsd-current@freebsd.org Subject: Re: NFS write() calls lead to read() calls? Message-ID: <7ad7ddd90703280611p5c0ca4e1y600315551391a813@mail.gmail.com> In-Reply-To: <eudfat$g2m$1@sea.gmane.org> References: <7ad7ddd90703280238r5dd3f30ftc1641926ecdf44a8@mail.gmail.com> <eudfat$g2m$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/28/07, Ivan Voras <ivoras@fer.hr> wrote: > > The traffic flows like this: > > > > -----> -----> > > A B C > > <----- > > Have you tested with a small C program or a script to see if it's the > rewriting that's causing reads or is it some weird artifact of scp? I'm not a big user of scp(1), the reason this problem came up is because Samba has the same problem too. If our Windows Terminal server (over)writes onto the Samba-Export (which in turn is NFS mounted from the fileserver) then we get WRITE *and* READ calls. nfsstat -s shows that the READ column is increasing just as fast/slow as the WRITE column. So while I could work around scp anytime (tar|ssh is better in almost all cases) there is probably no way to work around Samba. What kind of C program or script did you have in mind? My C-foo is very weak ... Cheers, Uli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7ad7ddd90703280611p5c0ca4e1y600315551391a813>