large backups taking longer with 3.0.2
Hi All, I havn't compiled 3.0.3 pre1 yet but have been seeing considerable longer backup times on OSX 5.2, using 3.0.2 over 3.0.1. Has anyone else noticed this? The progress doesn't seem to show any problems or differences from 3.0.1 either. backing up 100+GB internal drive, with 1 million files, takes over 5 hours compared to 4 hours or less on 3.0.1. I can't seem to find any reason for this. Using options: -aHAXN --progress. Thanks, Rob -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: timeout in data send/receive (code 30) at /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153)
As an update to this problem, it seems that rsync has no problem updating/transferring the directory tree (every day, new data is added in a date directory structure at the remote site). So when I rsync, I get the new folders, but the error message always pops up before data files are transferred over. -- View this message in context: http://www.nabble.com/rsync-error%3A-timeout-in-data-send-receive-%28code-30%29-at--home-lapo-packaging-tmp-rsync-2.6.3-io.c%28153%29-tp17127523p17151640.html Sent from the Samba - rsync mailing list archive at Nabble.com. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5455] New: destination files with resource forks now have current mtime
https://bugzilla.samba.org/show_bug.cgi?id=5455 Summary: destination files with resource forks now have current mtime Product: rsync Version: 3.0.2 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Suppose LaCie Disk B is already a proper backup of LaCie Disk A rsync -aE /Volumes/LaCie\ Disk\ A/ /Volumes/LaCie\ Disk\ B No files will be copied since B is already the same as A, but any files with resource forks will now have their last-modified times changed to the current time on the destination disk. Now running the same command again will cause rsync to recopy those files due to the differing last-modified times. This will cause the last-modified times to revert to what they were before. The result is that every other time you run the command, any files with resource forks will be recopied, even though they haven't changed. I noticed this because I have some 50GB files with resource forks that never change (raw video files). The filesystems on both drives read as Mac OS Extended. The filesystem for the computer reads as Mac OS Extended (Journaled). The OS is Mac OS X 10.5.2 -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
