Re: rsync-2.6.2: NFS clients confused after an rsync

2004-05-11 Thread Brian Childs
On Tue, May 11, 2004 at 11:22:27AM -0700, Wayne Davison wrote: > On Tue, May 11, 2004 at 01:48:33PM -0400, Brian Childs wrote: > > Yes. Without the -b, it doesn't happen. > > OK, I think I know why now: without -b the old inode goes away, and > thus NFS gets some indic

Re: rsync-2.6.2: NFS clients confused after an rsync

2004-05-11 Thread Brian Childs
On Tue, May 11, 2004 at 10:01:48AM -0700, Wayne Davison wrote: > On Thu, May 06, 2004 at 06:21:55PM -0400, Brian Childs wrote: > > rm -f /tmp/testpath/* $HOME/testpath/* > > > > #Prime it > > echo some data > /tmp/testpath/testfile > > sleep 1 > > rsync

Re: rsync-2.6.2: NFS clients confused after an rsync [PATCH included]

2004-05-11 Thread Brian Childs
On Fri, May 07, 2004 at 11:18:46AM -0400, Brian Childs wrote: > As a response to my original post, here's a patch that implements my > proposed solution. > > I've tested it, and it fixes the problem, but I'm afraid there may be > some hidden consequences of doing t

Re: rsync-2.6.2: NFS clients confused after an rsync [PATCH included]

2004-05-07 Thread Brian Childs
fname, (long) modtime, On Thu, May 06, 2004 at 06:21:55PM -0400, Brian Childs wrote: > We use rsync to update an nfs server. After an update, we noticed that > a large number of clients didn't see the updated data. > > It took me a while to be able to reliably reproduce this proble

rsync-2.6.2: NFS clients confused after an rsync

2004-05-06 Thread Brian Childs
We use rsync to update an nfs server. After an update, we noticed that a large number of clients didn't see the updated data. It took me a while to be able to reliably reproduce this problem, but it happens on old and new versions of rysnc. It also happens across all the platforms we use here (s