Problem remote sync with several directories/files
Hi, does anyone know what is wrong with that command line ? rsync -e /path to ssh/ssh -i/keypath/.ssh/id_rsa -vaoRrn [EMAIL PROTECTED]:'/root/directory/./dirToSync1' :'/root/directory/./dirToSync2' '/dir/to/destination' Calling it with real paths the rsync command overview arises. Thanks for your efforts. Best Regards. Christoph Unbegrenzter Speicher, Top-Spamschutz, 120 SMS und eigene E-MailDomain inkl. http://office.freenet.de/dienste/emailoffice/produktuebersicht/power/mail/index.html -- 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 to servers highly sensitive to IO load
Perfect! It sounds like --append it the magic bullet in this case... Thanks, Jeff Wayne Davison wrote: On Fri, Jul 11, 2008 at 10:10:16AM -0400, Jeff Woods wrote: --bwlimit=17 --partial --append You only want to use --append if you can guarantee that the files will not have any changes in the existing data on the receiving side. A modern rsync does not compute a full-file checksum for --append unless you use a second --append, since that slows down the appending. If you're using -c (--checksum), you probably don't want to do that, since that's super slow. Just use -t (--times) and let the normal size+mtime check look over things for you. If you find that you really need checksumming, you might want to look at the db.diff in the patches dir that lets you cache checksums in a DB (i.e. SQLite or MySQL) and associate them with unchanged files (since it matches a file's size, mtime, ctime, and inode, it is safe). If the source of the I/O is rsync's scanning of the directories (not the checksumming of the files), you may want to look into the slow-down.diff file in the patches dir, as that provides a way to get rsync to do its directory scanning more slowly. negating the need to re-read the entire file for a post-transfer checksum There is no such thing in rsync, since it computes the checksum as the file is written. ..wayne.. - The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.-- 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: some files could not be transferred (code 23) at main.c (1506)
On 7/11/2008 3:11 PM, Jeff MacDonald wrote: I'm trying to rsync a fairly large chunk of data [around 350 gigs, mostly 1 gig files] between 2 hosts in separate colo facilities. Link is plenty fast, I can pull 10 megs easily. Everytime, it seems to die with something like this, whether I try rsync from the stable 2 branch or the beta 3 branch With that many large files, my first guess would be not enough RAM? Hrmmm not sure , the linux machine has 512 megs and the solaris 2 gigs. i guess teh solaris machine has nothing to do with this tho. What version of rsync at each end? I'm a bit embarrassed, I didn't read my errors close enough and it's a simple permission denied error. Thanks charles :) -- 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: some files could not be transferred (code 23) at main.c (1506)
On 11-Jul-08, at 5:04 PM, Wayne Davison wrote: On Fri, Jul 11, 2008 at 09:58:21AM -0300, Jeff MacDonald wrote: Everytime, it seems to die with something like this [...] rsync error: some files could not be transferred (code 23) at main.c(1506) That's not dying, that's completing its run and letting you know that some files could not be transferred during the run. See the earlier errors that rsync output for specifics (e.g. unopenable files, etc.). ..wayne.. I'm a bit embarrassed, I didn't read my errors close enough and it's a simple permission denied error. Thanks 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
DO NOT REPLY [Bug 3653] Reduce the need for the vanished files warning
https://bugzilla.samba.org/show_bug.cgi?id=3653 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #13 from [EMAIL PROTECTED] 2008-07-14 16:24 CST --- Guys, I also find this warning annoying. I get a pretty much daily email about it from my backup 'failing'. /etc/cron.daily/snapback2: rsync warning: some files vanished before they could be transferred (code 24) at main.c(1515) [generator=3.0.2] I am not even sure which files are vanishing. I suspect the files are from a mail directory, where some spam messages are moved after rsync builds the files list. I vote for including the patch into rsync to make it more useful for this use case. -- 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
Re: Problem remote sync with several directories/files
On Mon, 2008-07-14 at 13:42 +0200, [EMAIL PROTECTED] wrote: does anyone know what is wrong with that command line ? rsync -e /path to ssh/ssh -i/keypath/.ssh/id_rsa -vaoRrn [EMAIL PROTECTED]:'/root/directory/./dirToSync1' :'/root/directory/./dirToSync2' '/dir/to/destination' Calling it with real paths the rsync command overview arises. I don't see anything wrong with the command, but note that the syntax you're using for multiple remote source arguments is new in rsync 3.0.0; older rsync clients will reject it with an error. If your rsync is older than 3.0.0, try this syntax instead: rsync -e /path to ssh/ssh -i/keypath/.ssh/id_rsa -vaoRrn [EMAIL PROTECTED]:'/root/directory/./dirToSync1 /root/directory/./dirToSync2' '/dir/to/destination' Matt signature.asc Description: This is a digitally signed message part -- 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] rsync branch, master, updated. v3.0.3-9-gb8993a1
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 rsync. The branch, master has been updated via b8993a1ee98880dce130d2c47da4f5591b986e38 (commit) from 951e826b75c4a4e6bc066e248d7489fb6eba6fde (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 b8993a1ee98880dce130d2c47da4f5591b986e38 Author: Wayne Davison [EMAIL PROTECTED] Date: Mon Jul 14 07:40:10 2008 -0700 Made the info_verbosity array 1 element larger. --- Summary of changes: options.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- rsync ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
[SCM] rsync branch, master, updated. v3.0.3-10-gf35798a
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 rsync. The branch, master has been updated via f35798a57ed891efe18fb171e7004d77fcf51790 (commit) from b8993a1ee98880dce130d2c47da4f5591b986e38 (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 f35798a57ed891efe18fb171e7004d77fcf51790 Author: Wayne Davison [EMAIL PROTECTED] Date: Mon Jul 14 22:47:03 2008 -0700 Added a test_fail function to 00-hello.test. --- Summary of changes: testsuite/00-hello.test |5 + 1 files changed, 5 insertions(+), 0 deletions(-) hooks/post-receive -- rsync ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs