Re: error in logging (version 3.1.0)
On Sat, 2009-11-07 at 00:36 -0200, Carlos Carvalho wrote: I use rsync -ii so that it logs *all* actions. Further, I don't use any delete option but use --force. This means that if there's a name collision rsync deletes files or directories. Here's an example: 0 0*deleting rwxrwsr-x 1969/12/31-21:00:00 scm/linux/kernel/git/amit/vs-kernel.git/objects/38 0 0*deleting rwxrwsr-x 1969/12/31-21:00:00 scm/linux/kernel/git/amit/vs-kernel.git/objects I guess some ancestor of scm/linux/kernel/git/amit/vs-kernel.git/objects became a non-directory? That seems unlikely to me. Therefore I didn't expect to find any of these directories after the sync is finished. However I get: % ls scm/linux/kernel/git/amit/vs-kernel.git/objects 09 15 2d 82 a8 bc cf e0 ff It might be that for some reason rsync created the directory again. I don't think so. I only know of one rare case in which rsync would delete and recreate a directory, and I don't think it applies here: when the file list contains an ancestor and a descendant but not the directory itself, which can only happen with --relative --no-implied-dirs and protocol = 29. BUT *no other lines* with scm/linux/kernel/git/amit/vs-kernel.git/objects appear in the log. So we have two possibilities: either rsync lied and didn't delete the directory, or it created it again and didn't tell it in the log. Do you have a reproducible test case? -- Matt -- 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: Input/Output error 5 ?
On Thu, 2009-11-05 at 09:20 -0500, Michael W. Cocke wrote: What, exactly, does input/output error 5 mean? (Yes I googled it, but all I can find is a lot of people getting the error, not what it means). Typically, that there is something wrong with the filesystem or the disk, which is out of rsync's control. -- Matt -- 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, excluding files w/certain characteristics
Edward Peschko (horo...@gmail.com) wrote on 6 November 2009 18:46: I was wondering - is there an option to rsync which allows you to exclude transfers of files with a certain size or other characteristics? I want to setup a 'partial' rsync mirror where I only pull files under 5M, for example.. I see the option for including/excluding file names in the usage, but not file sizes.. They exist. See options --max-size and --min-size in the manual. -- 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: exit status 13 in version 3.1
On Wed, Nov 4, 2009 at 8:05 PM, Matt McCutchen m...@mattmccutchen.netwrote: With commit 84c11e85a4c4a12ecacba24afe9617222e4361e6, I get different output, but still not the desired No space left on device: Yeah, that's the long-standing issue where a fatal error on the server side can cause the client side to get a socket error trying to write to the socket before it has a chance to read the error(s) from the socket. The latest git archive finally has a fix for this. It should make the exit messages much cleaner for an abnormally-exiting protocol 31 transfer, both receiving the final error from the server and exiting with the proper error code. When an older client is talking to a new server, the error should also make it to the client, but the client will exit with the (sadly) traditional error about an unexpectedly closed connection. ..wayne.. -- 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
Ideas needed: getting error cannot set time on server ...
Insufficient permissions I am running a n rsync script on MAC OS 10.4 clients - runs OK with a Windows 2003 server but getting this error when talking to an Apple Server running OS X 10.5.7 It is a basic rsync as follows: copying, with sync from client to server volume RETeensData that is mounted on the client rsync -av /Users/Shared/'RE Teens Data'/ /Volumes/RETeensData/ As newbie to rsync any ideas are appreciated. Thanks, Lew Brentano Ripple Effects, Inc -- 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: exit status 13 in version 3.1
On Sat, 2009-11-07 at 09:38 -0800, Wayne Davison wrote: On Wed, Nov 4, 2009 at 8:05 PM, Matt McCutchen m...@mattmccutchen.net wrote: With commit 84c11e85a4c4a12ecacba24afe9617222e4361e6, I get different output, but still not the desired No space left on device: Yeah, that's the long-standing issue where a fatal error on the server side can cause the client side to get a socket error trying to write to the socket before it has a chance to read the error(s) from the socket. The latest git archive finally has a fix for this. I tested commit 2907af472d1f33b3c422cb9f601c121b242aa9c7 and, again, the output is different but the problem is not fixed: $ rsync-dev big-file small-fs/ rsync: connection unexpectedly closed (146 bytes received so far) [sender] $ rsync-dev --msgs2stderr big-file small-fs/ rsync: write failed on /PATH/TO/small-fs/big-file: No space left on device (28) rsync: connection unexpectedly closed (36 bytes received so far) [sender] rsync error: error in file IO (code 11) at io.c(181) [receiver=3.1.0dev] -- Matt -- 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
[SCM] The rsync repository. branch, master, updated. v3.0.3-263-gf918520
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project The rsync repository.. The branch, master has been updated via f9185203ee03152001530db5624a2b8c93e1ea94 (commit) from 84c11e85a4c4a12ecacba24afe9617222e4361e6 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit f9185203ee03152001530db5624a2b8c93e1ea94 Author: Wayne Davison way...@samba.org Date: Sat Nov 7 00:39:50 2009 -0800 Added notifications about error-exit values: - The receiver notifies the generator if it is exiting with an error, and then, if it is a server, waits around for the generator to die. This ensures that the client side has time to read the error. - The generator or sender will notifiy the other side of the transfer of an error-exit value if protocol 31 is in effect. This will get rid of some connection unexpectedly closed errors that are really expected events due to a fatal exit on the other side. --- Summary of changes: cleanup.c | 20 ++-- errcode.h |2 ++ io.c | 22 +- log.c |3 ++- rsync.h |3 ++- 5 files changed, 45 insertions(+), 5 deletions(-) hooks/post-receive -- The rsync repository. ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
[SCM] The rsync repository. branch, master, updated. v3.0.3-266-g2907af4
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project The rsync repository.. The branch, master has been updated via 2907af472d1f33b3c422cb9f601c121b242aa9c7 (commit) via 8346c62a95d601f2516059cccb4784fe36fe3e9d (commit) via 4655dcf218be15551c974a034b9c9f95e2505842 (commit) from f9185203ee03152001530db5624a2b8c93e1ea94 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 2907af472d1f33b3c422cb9f601c121b242aa9c7 Author: Wayne Davison way...@samba.org Date: Sat Nov 7 09:46:20 2009 -0800 Try to silence some warnings from checker. commit 8346c62a95d601f2516059cccb4784fe36fe3e9d Author: Wayne Davison way...@samba.org Date: Sat Nov 7 09:46:01 2009 -0800 Mention the error improvements. commit 4655dcf218be15551c974a034b9c9f95e2505842 Author: Wayne Davison way...@samba.org Date: Sat Nov 7 09:45:43 2009 -0800 Give noop_io_until_death() a time limit. --- Summary of changes: NEWS |5 + io.c |3 ++- log.c |2 +- main.c|2 +- options.c | 12 +++- 5 files changed, 16 insertions(+), 8 deletions(-) hooks/post-receive -- The rsync repository. ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
