search for: rerr_parti

...my setup for at least 2 or 3 years now. I've been very happy with its performance. The rsync version reported on all machines is 3.0.7 from the debian testing package of the same version (see attached lis). As of late, all the pushes to my home server end up with rsync exiting with code 23 (RERR_PARTIAL). I can't quite reconcile why this is. * Backing up from /mnt/snapshots/khellman means that the process creating the file list should see an immutable version of my HOME. If my fetchmail process runs from cron, it changes the logical volume contents mounted at my HOME, but /mnt/snapsho...

https://bugzilla.samba.org/show_bug.cgi?id=9416 Summary: --files-from : RERR_PARTIAL vs RERR_VANISHED Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: penning at uu.nl...

...d, created, or modified by the application whilst rsync is running. I am getting the following output line, in amongst lots of succesful transfers, when running rsync, : send_files failed to open //ca/spool/smdiq/005.973416/9734161182.1: No such file or directory This then results in an RC of 23 (RERR_PARTIAL), I believe this is happening because between the time rsync compiles the file list and the time rsync attempts to transfer the file the application has deleted it. My problem here is that rsync is run as part of a script that performs the backup and the script must be able to detect whether th...

...ot;missing_args" value is transferred when set ; and (2) in rsync.c, in the "missing_args" case, replace FERROR_XFER with something else, since apparently any log message with logcode FERROR_XFER sets the flag 'got_xfer_error' in log.c, and that finally leads to exit code RERR_PARTIAL (23), which is what we are trying to avoid. I am currently testing this on fairly big datasets to see if there's something missing, and will write more when I see how it goes ( as I said, the data sets are fairly large ). There shall be a better way to address that, but this is all I can...

...eanup_pipe[0], &tmp, 1); ! } while (status == -1 && errno == EINTR); ! if (status != 1) { ! rprintf(FERROR,"cleanup read returned %d in do_recv\n", status); ! if (status == -1) ! rprintf(FERROR,"with errno %d (%s)\n", errno, strerror(errno)); ! _exit(RERR_PARTIAL); ! } ! _exit(0); } close(recv_pipe[1]); close(error_pipe[1]); + close(cleanup_pipe[0]); if (f_in != f_out) close(f_in); io_start_buffering(f_out); *************** *** 462,469 **** io_flush(); io_set_error_fd(-1); ! kill(pid, SIGUSR2); ! wait_process(pid, &amp...

...t(bf(RERR_STREAMIO 12)) Error in rsync protocol data stream @@ -1126,6 +1128,7 @@ dit(bf(RERR_SIGNAL 20)) Received SIGUSR1 or SIGINT dit(bf(RERR_WAITCHILD 21)) Some error returned by waitpid() dit(bf(RERR_MALLOC 22)) Error allocating core memory buffers +dit(bf(RERR_PARTIAL 23)) Partial transfer dit(bf(RERR_TIMEOUT 30)) Timeout in data send/receive enddit()

...g_list_push(NORMAL_FLUSH); @@ -837,6 +891,19 @@ } sleep_for_bwlimit(ret); + + if( timelimit ) { + time_expired = has_timelimit_expired(); + if( 1 == time_expired ) { + rprintf(FERROR, RSYNC_NAME ": \n%d minute time limit exceeded.\n", timelimit); + exit_cleanup(RERR_PARTIAL); + } + } + + if( stopat && has_stopat_expired() ) { + rprintf(FERROR, RSYNC_NAME ": \n%s stopat time exceeded.\n", stopat); + exit_cleanup(RERR_PARTIAL); + } total += ret; diff -urN rsync-2.6.1pre-2/options.c rsync-2.6.1pre-2_modified/options.c --- rsync...

I seem to get an exit status 23 once or twice a day, or about 2 times out of 50 runs. 23 is not listed in the documentation. Can anybody clue me into what the 23 error is ??? The information contained in this e-mail including any attachments may constitute Corvis Corporation Proprietary Information that is subject to Non-Disclosure Agreement and cannot be disclosed to any other party without

...This does seem to happen more often on NT4 Server though. I am using the following parameters with rsync: -rtlD --delete --numeric-ids When googling for a solution i found the folling link : http://lists.samba.org/archive/rsync/2003-August/006812.html Which states the " rsync returns 23 (RERR_PARTIAL) when a file has been deleted after the list has been created " . This does not make much sence to me but maybe someone else can make sense of it. Any help/comments please ?. Thank you. Ian Legal Disclaimer: Any views expressed by the sender of this message are not necessarily those of Co...

...told about the typo themselves :-) --- log.c.orig 2004-08-17 10:25:57.000000000 +0200 +++ log.c 2004-09-05 16:28:42.000000000 +0200 @@ -61,7 +61,7 @@ { RERR_WAITCHILD , "some error returned by waitpid()" }, { RERR_MALLOC , "error allocating core memory buffers" }, { RERR_PARTIAL , "some files could not be transferred" }, - { RERR_VANISHED , "some files vanished before they could be transfered" }, + { RERR_VANISHED , "some files vanished before they could be transferred" }, { RERR_TIMEOUT , "timeout in data send/receive"...

...N_TIMEOUT 35 + /* Although it doesn't seem to be specified anywhere, * ssh and the shell seem to return these values: * diff -Naur rsync-2.6.8/log.c rsync-2.6.8-new/log.c --- rsync-2.6.8/log.c Sat Apr 8 19:04:34 2006 +++ rsync-2.6.8-new/log.c Wed May 24 16:19:27 2006 @@ -83,6 +83,7 @@ { RERR_PARTIAL , "some files could not be transferred" }, { RERR_VANISHED , "some files vanished before they could be transferred" }, { RERR_TIMEOUT , "timeout in data send/receive" }, + { RERR_CON_TIMEOUT, "timeout in connect()" }, { RERR_CMD_FAILED , &quot...

...ng from the server during the file transfers. So now it also (incorrectly) exits with a 0 exit code in the case of partial transfers from a 2.6.0 server. So this needs some work... - On the server, if the client protocol is < 27, use FERROR instead of FINFO so the pre-2.6.0 client can use a RERR_PARTIAL exit code. - On the client side, it has to somehow recognize the vanished error on the server. It could examine each FINFO message that comes over to see if it begins with "file has vanished:" and set the IOERR_VANISHED flag (but that's pretty kludgy...). I haven't code...

...value is transferred > when set ; and > (2) in rsync.c, in the "missing_args" case, replace FERROR_XFER with > something else, since apparently any log message with logcode > FERROR_XFER sets the flag 'got_xfer_error' in log.c, and that finally > leads to exit code RERR_PARTIAL (23), which is what we are trying to avoid. > > I am currently testing this on fairly big datasets to see if there's > something missing, and will write more when I see how it goes ( as I > said, the data sets are fairly large ). > > There shall be a better way to address...

...value is transferred > when set ; and > (2) in rsync.c, in the "missing_args" case, replace FERROR_XFER with > something else, since apparently any log message with logcode FERROR_XFER > sets the flag 'got_xfer_error' in log.c, and that finally leads to exit > code RERR_PARTIAL (23), which is what we are trying to avoid. > > I am currently testing this on fairly big datasets to see if there's > something missing, and will write more when I see how it goes ( as I said, > the data sets are fairly large ). > > There shall be a better way to address th...

...error in IPC code" }, { RERR_SIGNAL , "received SIGUSR1 or SIGINT" }, + { RERR_CRASH , "*** WE HAVE CRASHED :-( ***" }, { RERR_WAITCHILD , "some error returned by waitpid()" }, { RERR_MALLOC , "error allocating core memory buffers" }, { RERR_PARTIAL , "some files could not be transferred" }, diff -ur rsync-2.6.6/main.c rsync/main.c --- rsync-2.6.6/main.c Thu May 12 11:43:14 2005 +++ rsync/main.c Sat Jan 28 06:29:06 2006 @@ -114,6 +114,14 @@ * message describing the purpose of the child. Also indicate * this to the caller so...

...return these values: * Common subdirectories: rsync-2.6.3/lib and rsync-2.6.3_jdb/lib diff -c rsync-2.6.3/log.c rsync-2.6.3_jdb/log.c *** rsync-2.6.3/log.c Sun Sep 5 21:30:00 2004 --- rsync-2.6.3_jdb/log.c Tue Mar 15 19:47:19 2005 *************** *** 63,68 **** --- 63,69 ---- { RERR_PARTIAL , "some files could not be transferred" }, { RERR_VANISHED , "some files vanished before they could be transferred" }, { RERR_TIMEOUT , "timeout in data send/receive" }, + { RERR_LOG_NOTOPENED, "log file could not be opened" },...

...ransferred when set ; and > (2) in rsync.c, in the "missing_args" case, replace FERROR_XFER with > something else, since apparently any log message with logcode > FERROR_XFER sets the flag 'got_xfer_error' in log.c, and that > finally leads to exit code RERR_PARTIAL (23), which is what we are > trying to avoid. > > I am currently testing this on fairly big datasets to see if there's > something missing, and will write more when I see how it goes ( as I > said, the data sets are fairly large ). > > There shall be...

...problem: we are talking about a marginally small number of files ( a few hundred of at least hundreds of thousands, sometimes millions ), with their mtimes messed up possibly because of some subtle fault in the filesystem implementation. However, these very few files make rsync to set return code RERR_PARTIAL (23) for the whole transfer, what leaves us with no good options. In my experience, on a Linux system with utimensat() / futimens() the latter fails to transfer a negative .st_mtim.tv_nsec, or a value greater than 1000000000 with errno 22 (EINVAL). However, since rsync 3.1.1 seems to compare on...

...msg_list_push(NORMAL_FLUSH); @@ -837,6 +859,14 @@ } sleep_for_bwlimit(ret); + if( timelimit ) { + time_expired = has_timelimit_expired(); + if( 1 == time_expired ) { + rprintf(FERROR, RSYNC_NAME ": \n%d minute time limit exceeded.\n", timelimit); + exit_cleanup(RERR_PARTIAL); + } + } + total += ret; diff -urN rsync-2.6.1pre-2/options.c rsync-2.6.1pre-2_modified/options.c --- rsync-2.6.1pre-2/options.c 2004-04-17 13:07:23.000000000 -0400 +++ rsync-2.6.1pre-2_modified/options.c 2004-04-19 16:07:57.000000000 -0400 @@ -83,6 +83,7 @@ int copy_unsafe_li...