Re: does partial option work over ssh?
On Fri 14 Jul 2006, Glen Davison wrote: This is what I believe SHOULD work, but it doesn't: rsync -aP -e 'ssh -c blowfish' [EMAIL PROTECTED]:/path/to/file1/ newpath/ - it just starts again. The interrupted rsync session also needs to have had the --partial option (implied here by -P) active, otherwise the interrupted session will have discarded the partial data. If --partial _was_ in effect, then how did you determine it starts again? Remember that rsync will still verify the contents of the partial transfer, i.e. use checksums to verify the data already there. That may look like it's transferring again. If you want to skip that, use --append to just append data. Both machines are behind firewalls, but going in the above direction should be okay; plus of course it does succeed in copying, just not in appending. A colleague here says he has tried to do the same thing, and he could get it to work for an rsync daemon, but not over ssh. The underlying transport is not relevant. Paul Slootman -- 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 3935] New: replacing a full directory with symlink with --delete-after produces cryptic message
https://bugzilla.samba.org/show_bug.cgi?id=3935 Summary: replacing a full directory with symlink with --delete- after produces cryptic message Product: rsync Version: 2.6.6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] What Happned: On the source, a directory with files is changed to a symlink. rysnc -ra --delete-after will then generate the following message: rsync: delete_file: rmdir /tmp/rsync.bug.11080/dest/somedir failed: Directory not empty (39) rsync error: some files could not be transferred (code 23) at main.c(791) What I Expected: I expected the directory to be replaced with a symlink (like --delete would have done) OR I expected the directory to be deleted at the end (because of --delete-after) but the symlink not to be sync'ed. I would expect it to still raise an error, but the next run would fix it (since the directory is done). OR I expected the error message to explain how I could fix this problem. I can see why it would fail during the sync phase, but the delete phase should have deleted it after the syncing part, since no IO errors were detected on the sending side. I have attached a simple script to generate this error on command. Ciao! -- 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. -- 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 3935] replacing a full directory with symlink with --delete-after produces cryptic message
https://bugzilla.samba.org/show_bug.cgi?id=3935 --- Comment #1 from [EMAIL PROTECTED] 2006-07-14 10:25 MST --- Created an attachment (id=2034) -- (https://bugzilla.samba.org/attachment.cgi?id=2034action=view) A test case This script will leave a /tmp/rsync.bug. directory around if it fails (which it does in the current version of rsync). You may want to clean up after the script before running it so that only one directory hangs around. Ciao! -- 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. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Autoreply from [EMAIL PROTECTED] [Re: test ]
-- 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 3935] replacing a full directory with symlink with --delete-after produces cryptic message
https://bugzilla.samba.org/show_bug.cgi?id=3935 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED Version|2.6.6 |2.6.7 --- Comment #2 from [EMAIL PROTECTED] 2006-07-14 20:39 MST --- Firstly, thanks for the detailed bug-report. This bug was fixed in 2.6.7: - Got rid of the need for --force to be used in some circumstances with --delete-after (making it consistent with --delete-before/-during). So, you can either upgrade to 2.6.8, or use the --force option when using --delete-after. -- 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. -- 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: Backup and renaming old file that became directory
On 7/12/06, Yan Morin [EMAIL PROTECTED] wrote: rsync: keep_backup failed: /mnt/backup/foo/home/bar - /mnt/backup/foo/old/home/bar: Is a directory (21) [...] Oh, you're right! I guess I didn't set up the scenario correctly the first time, because now I get a messy error similar to yours. I will investigate further. Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
