Re: patch for replacing non-printable chars in filenames
Hi. After trying this a bit, I now think it would read better to use 3-digit octal escaping. I would be perfectly fine with that. And octal is probably more in the line of how escaping is traditionally done. As long as I can process the files in the log, I'm all for it. Btw, will this change make it into a later rsync version (2.4.7?) ? I would rather not depend on using a custom patched rsync, but if it will become a standard feature at some point it feels less hacky. ;) Anyway, thanks. :) Vidar -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 2561] rsync crashes when using the exclude from option on server side.
https://bugzilla.samba.org/show_bug.cgi?id=2561 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-04-01 09:22 --- Patch fixes the problem. Thanks for the fast response. -- 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: patch for replacing non-printable chars in filenames
On Fri, Apr 01, 2005 at 10:26:18AM +0200, Vidar Madsen wrote: Btw, will this change make it into a later rsync version ? Yes, I've just committed it for 2.6.5. Now I need to add configure checking for setlocale() and locale.h. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Rsync over an NFS mount (Scanned @ Decoma)
If I perform an local rsync with the 'delete' option over an NFS mount, and the mount point has been unmounted, the rsync will delete what was once on the local box.. For example Machine 1(192.168.0.1) is a live production server with a database within the /DB directory Machine 2 (192.168.0.2) is an idling server, capturing all changes of Machine 1's database. The rsync is done over an NFS mount onto machine 1, rather than via rsync client/server From Machine 2 : mkdir /mnt/plantx mount 192.168.0.1:/DB/plantx /mnt/plantx rsync -av --delete 127.0.0.1:/mnt/plantx/ /DB/plantx -e ssh Now , If I reboot machine 2, and forget to do the NFS mount, (actually the above rsync is in a crontab entry to happen automatically), then the /DB/plantx will be empty due to the 'delete' option of the rsync statement. I would assume this is a bug ??? (Embedded image moved to file: pic01842.jpg) CONFIDENTIALITY NOTE: This message may contain information that is privileged or confidential. As such, if you are not the intended recipient, please delete this message without retaining, distributing or copying all or any portion of its contents and notify us immediately of your receipt by return message to the sender or by calling our office at (905) 669-2888. Thank you in advance for your assistance.attachment: pic01842.jpg-- 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 over an NFS mount (Scanned @ Decoma)
Hi, On Fri, 1 Apr 2005 [EMAIL PROTECTED] wrote: If I perform an local rsync with the 'delete' option over an NFS mount, and the mount point has been unmounted, the rsync will delete what was once on the local box.. This is correct behaviour, if the source directory is empty. Ckeck if mounted before invoking rsync. Cheers -e -- Eberhard Moenkeberg ([EMAIL PROTECTED], [EMAIL PROTECTED]) -- 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: pauses sync'ing between tmpfs and disk on Linux 2.4.x
Thanks for the response, Tim.. I think I identified my bottleneck. Should have been pretty obvious. There are quite a few processes writing to / creating the files I'm rsync'ing. If I disable the daemon that handles this before rsync'ing, the speed of the rsync is quite fast. Must be some locking issue with files open for write while rsync tries to read them. D'oh! Thanks again. Ray On Sat, Mar 26, 2005 at 09:32:05AM -0800, Tim Moore wrote: I use rsync similarly. In addition to he standard /tmp traffic, junkbuster has a 4MB jarfile and 18MB log, ccache has 16 directories and 8000 files of which 3000 are 10k. Both are heavily used. -- 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 over an NFS mount (Scanned @ Decoma)
[EMAIL PROTECTED] wrote: Now , If I reboot machine 2, and forget to do the NFS mount, (actually the above rsync is in a crontab entry to happen automatically), then the /DB/plantx will be empty due to the 'delete' option of the rsync statement. I would assume this is a bug ??? Um.why wouldn't you have the NFS share automatically mount at boot time (fstab)? And/or, like Mr. Moenkeberg suggested: NFS_MNT=/mnt/plantx MOUNT_CHK=`/bin/mount -l | /bin/grep $NFS_MNT | /usr/bin/wc -l` if [ $MOUNT_CHK = 1 ] rsync... exit 0 else echo D'oh! You didn't mount the NFS share again! /var/log/rsync.log exit 1 fi Works for bash on linux anyways. Tis what I do for local backups to a USB drive. Gotta make sure it's actually plugged in or else your harddrive fills up REALLY quick. -john -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Rsync 2.6.4 Multiplexing Overflows when File Name Too Long (cwRsync)
I installed the newly released version of cwRsync today on a few Windows machines and have noticed a new problem that I have not seen mentioned anywhere. When syncing to an NT machine used for backups, my rsync client exited at the end of the transfer with the following message to standard error: multiplexing overflow 1:296 [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(777) The server daemon logs the following error regarding a file with a name that is too long before this error: 2005/04/01 13:01:43 [365] rsync: mkstemp (very long file name removed).000679 (in backup) failed: File name too long (91) 2005/04/01 13:01:43 [365] (various other files being backed up, all with same timestamp) 2005/04/01 13:01:43 [365] rsync: writefd_unbuffered failed to write 12 bytes: phase unknown [generator]: Connection reset by peer (104) 2005/04/01 13:01:43 [365] rsync error: error in rsync protocol data stream (code 12) at io.c(1080) There is no mention of this long file name error in the standard error or standard out of the client rsync process. Incidentally, this is an error I have seen for a long time with previous versions of rsync, but it was always visible in the standard error from the client. Although the transfer appears to have completed (i.e. everything has syncs up as expected), the client then exists without printing the statistics it normally does (it is invoked with --stats). In addition, the client actually exits with a status code of 3072, not 12 as indicated by the standard error message. The binary-aware reader may notice that this is actually 12 * 256. Interestingly, when I manually copied the offending long-named file to the server and reran the rsync session, the program terminated successfully with the normal some files could not be transferred status I am used to. This was also multiplied by 256 in the client rsync process exit code to become 5888 instead of 23. I'm sure the exit code anomaly is not related to the multiplexing error I am experiencing, which is the main problem I am having. So far this observation has been made on one out of one clients that I have tested. I was able to repeat this error several times on this machine before I discovered the message in the server log pointing me to the long file name problem. I am running a test from another client to duplicate this problem, but this process will not finish for at least another half hour. I will report back when I know if this happens on that system as well. Otherwise, I am a very happy rsync user of many years. Thanks for a great example of what FOSS can accomplish. -Ben : ) -- 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 over an NFS mount (Scanned @ Decoma)
Hi, On Fri, 1 Apr 2005, John Jablonski wrote: [EMAIL PROTECTED] wrote: Now , If I reboot machine 2, and forget to do the NFS mount, (actually the above rsync is in a crontab entry to happen automatically), then the /DB/plantx will be empty due to the 'delete' option of the rsync statement. I would assume this is a bug ??? Um.why wouldn't you have the NFS share automatically mount at boot time (fstab)? And/or, like Mr. Moenkeberg suggested: NFS_MNT=/mnt/plantx MOUNT_CHK=`/bin/mount -l | /bin/grep $NFS_MNT | /usr/bin/wc -l` if [ $MOUNT_CHK = 1 ] rsync... exit 0 else echo D'oh! You didn't mount the NFS share again! /var/log/rsync.log exit 1 fi Works for bash on linux anyways. Tis what I do for local backups to a USB drive. Gotta make sure it's actually plugged in or else your harddrive fills up REALLY quick. ... easier, and a simple prefix without a nesting level: NFS_MNT=/mnt/plantx mount | grep $NFS_MNT /dev/null if [ ! $? = 0 ]; then echo source not mounted, nothing done, exit 99 fi Cheers -e -- Eberhard Moenkeberg ([EMAIL PROTECTED], [EMAIL PROTECTED]) -- 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 2.6.4 Multiplexing Overflows when File Name Too Long (cwRsync)
Benjamin Watkins wrote: So far this observation has been made on one out of one clients that I have tested. I was able to repeat this error several times on this machine before I discovered the message in the server log pointing me to the long file name problem. I am running a test from another client to duplicate this problem, but this process will not finish for at least another half hour. I will report back when I know if this happens on that system as well. I can now confirm that this seems to happen whenever there is a long file name error. This appears to cause a corruption in the protocol stream. -Ben : ) -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
--compare-dest and preserving attributes change
Wayne Davison wrote: Earlier in the development cycle, I noticed that rsync was not updating a file that differed in attributes when using --compare-dest, so I decided to fix that for 2.6.4. Does this also fix the problem I reported in: http://lists.samba.org/archive/rsync/2005-February/011746.html or is this something different? It certainly *sounds* close, but the NEWS file didn't specify what was meant by attributes. - Andrew -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
HP-UX 11i and largefiles on rsync
For all you folks out there using rsync on HP-UX, be warned that HP-UX is still broken with regard to large files. I opened a bug report with HP last year, as described here: http://lists.samba.org/archive/rsync/2004-July/010226.html I've been periodically checking on the status and today I was told that it's been officially filed as a we won't fix this, citing that the mkstemp() library call wasn't mentioned in the /usr/share/doc/lg_files.txt document. (For some reason HP favors using the insecure tmpfile() call instead.) Despite HP's intransigence, I'd like to have an rsync that builds out of the box with working large file support. I figure there are several ways to accomplish this, and I'd like some input on the best way to proceed. I've come up with five possible options, though if anyone has an idea not listed here, please feel free to suggest it! 1) Change the autoconf environment to build rsync as a 64-bit binary by default on HP-UX. This results in a working mkstemp() but gives a binary that won't work on ancient HP hardware. 2) Change the autoconf environment to detect HP-UX and unset HAVE_SECURE_MKSTEMP even though the test for it succeeded. This would fall back to mktemp() very much like the manual process I use now, but would be automatic. This also means that if HP-UX were ever fixed (HA!), the new mkstemp() wouldn't get used. 3) Write a new autoconf test for a broken mkstemp() by creating a large sparse file in the current directory and automatically unsetting HAVE_SECURE_MKSTEMP. This would work on non-HP systems that were similarly broken and allow the use of mkstemp() if HP-UX were ever fixed (HA!) This may falsely fail if the current filesystem doesn't allow for large files (common on HP systems) and if the system doesn't support sparse files this test could fill up the filesystem. 4) Implement HP's suggested workaround of a fcntl() to set O_LARGEFILE on the file handle returned by mkstemp() inside syscall.c. This is essentially non-portable and indeed won't even work on HP-UX if building a 64-bit binary. 5) Document the workarounds for HP-UX in the INSTALL file (e.g. comment out HAVE_SECURE_MKSTEMP in config.h after running configure but before running make, or build a 64-bit binary.) What do you all think the best approach would be? I'd suggest #5 at a minimum. -- Steve -- 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: --compare-dest and preserving attributes change
On Fri, Apr 01, 2005 at 04:58:07PM -0500, Andrew Gideon wrote: Does this also fix the problem I reported in: http://lists.samba.org/archive/rsync/2005-February/011746.html No, rsync doesn't yet handle ACLs. I believe that the rawhide version of rsync (for redhat) is going to be patched to work with extended attributes, so hopefully we'll get something integrated into rsync before too long (I haven't had time to work on this because none of the systems I use have extended-attribute enabled). ..wayne.. -- 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: HP-UX 11i and largefiles on rsync
On Fri, Apr 01, 2005 at 03:36:59PM -0800, Steve Bonds wrote: Despite HP's intransigence, I'd like to have an rsync that builds out of the box with working large file support. I attempted a fix for this by having the code not use mkstemp() if open64() was around but mkstemp64() was not. However, not having any HP systems around to test this on, I never heard if this was helpful or not. Apparently not. I'd prefer to add rules to configure that don't require trying to write a large sparse file or to use the O_LARGEFILE kluge, but I'm open to suggestions on whether creating a 64-bit binary is better than just disabling HAVE_SECURE_MKSTEMP for HP-UX. I think the latter would probably be good enough, if we just want to go that route. What's the best way to detect HP-UX, anyway? ..wayne.. -- 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: --compare-dest and preserving attributes change
On Fri, 2005-04-01 at 17:22 -0800, Wayne Davison wrote: No, rsync doesn't yet handle ACLs. I believe that the rawhide version of rsync (for redhat) is going to be patched to work with extended attributes, so hopefully we'll get something integrated into rsync before too long (I haven't had time to work on this because none of the systems I use have extended-attribute enabled). Anything I can do to help? I can get the ACL patch for .4, and then patch that with the fix I did last time if you'd like. - Andrew -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
CVS update: rsync
Date: Fri Apr 1 16:48:54 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv27894 Modified Files: util.c Log Message: Changed safe_fname() to output \### (octal) to escape non-printable characters (not ?) and \\ to escape \ itself. Revisions: util.c 1.181 = 1.182 http://www.samba.org/cgi-bin/cvsweb/rsync/util.c?r1=1.181r2=1.182 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Fri Apr 1 17:25:32 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv8713 Modified Files: configure config.h.in Log Message: Regenerated. Revisions: configure 1.208 = 1.209 http://www.samba.org/cgi-bin/cvsweb/rsync/configure?r1=1.208r2=1.209 config.h.in 1.100 = 1.101 http://www.samba.org/cgi-bin/cvsweb/rsync/config.h.in?r1=1.100r2=1.101 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Fri Apr 1 17:25:35 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv8824 Modified Files: configure.in Log Message: - Changed version to 2.6.5cvs. - Look for setlocale(), locale.h, and honor --disable-locale. Revisions: configure.in1.216 = 1.217 http://www.samba.org/cgi-bin/cvsweb/rsync/configure.in?r1=1.216r2=1.217 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Fri Apr 1 17:25:37 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv8846 Modified Files: main.c Log Message: - Conditionally include locale.h. - Conditionally call setlocale(LC_CTYPE, ). Revisions: main.c 1.268 = 1.269 http://www.samba.org/cgi-bin/cvsweb/rsync/main.c?r1=1.268r2=1.269 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Fri Apr 1 18:18:17 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv25179 Modified Files: NEWS Log Message: Mention fix for --compare-dest. Revisions: NEWS1.274 = 1.275 http://www.samba.org/cgi-bin/cvsweb/rsync/NEWS?r1=1.274r2=1.275 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs