similar to: better rsync error code when no space?

Hi All Some time rsync just return error code 23 that some files are not transferred. Is there a way to get a list of these files so we can retry it later time? For example, we scan the whole file system and N files are not transferred. Instead of scan the whole file system later again, we can use files-from which is much faster. Thanks. -- Ming Zhang @#$%^ purging memory... (*!%

Hi All I run rsync in an automated environment and it sometime will crash and leave a core dump file. from core dump, gdb shows that gdb) bt #0 add_dirs_to_tree (parent_ndx=-1, from_flist=0x56c590, dir_cnt=1) at flist.c:1422 #1 0x0000000000409eab in send_file_list (f=16, argc=-1, argv=0x56c238) at flist.c:2068 #2 0x0000000000419052 in client_run (f_in=16, f_out=16, pid=-1, argc=1,

Hi What should be the right exit code for vanished file in this scenario. (1) Use inotify or other mechanism to check changed files and then generate a file list. (2) < file get deleted> (3) run rsync with --files-from with the old list. then send_file_list()->link_stat() will return errno 2 on some files and then set exit code to 23. but shall rsync return 24? -- Ming Zhang

Hi All I tried to find out in the man page about what is the valid character we can use in module name in rsyncd.conf but failed. Anyone knows? Anyway, here is a bug. I defines a module with abc/def as name. $ rsync lab11-101:: abc/def this one show the module name, but when i try to use it. $ rsync vpn lab11-101::abc/def @ERROR: Unknown module 'abc' rsync error: error

Hi All I would like to use rsync to synchronize two file system tree over WAN periodically. The file system trees contain millions of small image files. Base on our understanding, rsync try to generate file name list before doing any operation, we easily run short of memory and have impact on our normal file system activities. I wonder if rsync can have an option that when it scan the file

Hi I have a file system that contains millions of small files. Since I backup it everyday with rsync using slow WAN link, I think it will be nice that if rsync can do this: An option that let rsync only check with remote rsync daemon about local files that has last modification time newer than one day ago (so is modified since yesterday backup). This can greatly reduce the WAN traffic. Is this

Hi All Tried to search the list but could not find anything about this. I have a rsync daemon running with starting cwd as /usr/local/bin. then after some io, and after all io finished, its cwd is /fs1 which is one of the module path. now i need to umount fs1 and i can not do it. is this a known issue or something worthy fix? not sure what else information i need to provide. thanks. -- Ming

Hi All We always run rsync with --files-from and sometime it gets a error code 23, partial transfer. is it possible to find out what files are not transferred without check the error message by human eye(since we want to do it in a script)? Thanks. -- Ming Zhang @#$%^ purging memory... (*!% http://blackmagic02881.wordpress.com/ http://www.linkedin.com/in/blackmagic02881

Hi All Any idea when the 3.0.0 will be rolled out? Thanks! -- Ming Zhang @#$%^ purging memory... (*!% http://blackmagic02881.wordpress.com/ http://www.linkedin.com/in/blackmagic02881 --------------------------------------------

Hi All This can be reproduced easily. run rsync under gdb and set a break point at read_timeout(). then after rsync talk with remote rsync daemon and stop at this function, turn off remote machine directly. then let rsync run and it will run forever in this function. if we just kill remote rsync daemon, it is fine and quickly detected, because OS do clean up work. But if power off the box

Hi All. On Mac OS10.4, using rsync 3.0, it stops during a transfer. I mount an SMB share, and then use the line: sudo rsync -avhi --delete --stats --timeout=360 --progress --log-file=/Volumes/backup/20080429/rsynclog.txt --exclude="*:*" /Volumes/RAID_One /Volumes/backup/20080429 There's a few terabytes of data, and it never finishes a complete run. It can stop at anywhere during

https://bugzilla.samba.org/show_bug.cgi?id=6183 Summary: rsync error file too large (27) Product: rsync Version: 3.0.4 Platform: Other OS/Version: AIX Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: brossob@gmail.com QAContact:

I've been having problems trying to sync two small partitions (128MB) that may be near to full. If rsync gets a write error (such as is caused when you fill up a partition) during a sync without the use of "-T", it will stop with this error: rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream

Hi All If rsync gets files from standard input, when it starts to process that file, immediately or read until EOF, or somewhere in between? For example, if a list is generated slowly but continuously and keep feeding to rsync, will rsync wait a very long time before ever handling the first file? Is this behavior controllable? Thanks! Ming -- never so busy...

[I sent this the other day, but it never got approved for the list] I've been having problems trying to sync two small partitions (128MB) that are usually near being full. The rsync would fail with this cryptic error: rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) It ends up

Typically rsync exits and reports an error such as: rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: write failed on "/Volumes/Backup/big_file.dmg": No space left on device (28) rsync: connection unexpectedly closed (67174 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at /src/ rsync-3.0.5/io.c(600)

https://bugzilla.samba.org/show_bug.cgi?id=5075 Summary: Syncing with --iconv may yield protocol error Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: lennart.samba@lovstrand.com

Hi, on HPUX 11i with ANSI/C compiler with largefile option. below rsync is on local file system. # rsync -av /prod1/* /prod1n/ building file list ... done DW/ DW/DATA/ DW/DATA/DWCOF02.DAT rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(836) rsync: writefd_unbuffered failed to write 69

Hello All: I'm having an issue with rsync in that it recently (11/29/2008) started to crash during a daily cron job backup. Below is some info on how rsync is being used to backup our servers. Version: 2.6.9 Execution: Called daily via a wrapper script, and up until about 2 weeks ago, ran fine. The wrapper script just loops through a series servers to backup. The first server

Hello, all... I've been trying for a week for transfer ~100 Gig of data using either rsync:// over IPSEC or tunneled through SSH, but it keeps failing... I have done as the documentation says and here are the results: I ran the following command: rsync -avz -vvv --dry-run --rsync-path=/root/bin/rsync-debug.sh -- delete-excluded --exclude-from=server-backup.exclusions --link-