Hi all! I'm syncing a windows share from a NetApp filer to a local partition on my RHEL3 box. I observe the following behavior: - rsync syncs more than neccessary, files that haven't changed since years - files that have been synced, aged for an hour or two on the netapp host Environment: cifs share mounted to /backup/sync (mount -t smbfs -o username=user,password=pwd //server/share /backup/sync) this user has only read rights on the windows share mirror the mounted cifs share to a local partition (rsync -a --delete-after /backup/sync/ /dest/dir) where is my problem? do I use the wrong switches? how is it possible that the files age a few hours on the source? Thank you all in advance for your help Juergen
On Wed 25 May 2005, Juergen Busam wrote:> > I'm syncing a windows share from a NetApp filer to a local partition on > my RHEL3 box. I observe the following behavior: > > - rsync syncs more than neccessary, files that haven't changed since years > - files that have been synced, aged for an hour or two on the netapp hostI can't quite parse that last sentence...> Environment: > > cifs share mounted to /backup/sync (mount -t smbfs -o > username=user,password=pwd //server/share /backup/sync)Why use CIFS? Netapp understands NFS like no one else... so use NFS!> this user has only read rights on the windows share > > mirror the mounted cifs share to a local partition (rsync -a > --delete-after /backup/sync/ /dest/dir)Using rsync over a "network drive" isn't that useful, rsync is meant to optimize network traffic between de sender and the receiver, possibly at the cost of more disk IO. In this case, disk IO on the sender *is* network traffic... Use -v (one or more times) to see exactly what's going on. Paul Slootman
On Wed, May 25, 2005 at 09:24:50PM +1000, Juergen Busam wrote:> how is it possible that the files age a few hours on the source?If you're running at least 2.6.4, use the -i option to see a summary of what differences rsync sees between the pairs of files. For instance, a summary like this:>f..t.... foobar.bazTells you that the timestamp was different (t) and that the file (f) was transferred to a local destination (>). Once you know what is different about the files, you'll be able to investigate how those differences got there. ..wayne..
I actually have to use rsync-2.5.7-5.3E which is included in RHEL3. I assume that the problem with the aging timestamps results in more files are transferred... I've no idea why the source timestamps are changed... Can anyone explain this?? Or does anyone has an idea why it could happen? Juergen Wayne Davison wrote:> On Wed, May 25, 2005 at 09:24:50PM +1000, Juergen Busam wrote: > >>how is it possible that the files age a few hours on the source? > > > If you're running at least 2.6.4, use the -i option to see a summary of > what differences rsync sees between the pairs of files. For instance, a > summary like this: > > >>f..t.... foobar.baz > > > Tells you that the timestamp was different (t) and that the file (f) was > transferred to a local destination (>). Once you know what is different > about the files, you'll be able to investigate how those differences got > there. > > ..wayne.. > >-- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html