similar to: Intermittent make_bak_dir mkdir "<path>" failed: File exists (17)

Yesterday I upgraded rsync from 2.6.9 to 3.0.2 (as part of upgrading Fedora 8 to Fedora 9). Today, I received these unexpected errors: rsync: make_bak_dir mkdir "/backup/server/../server-before-5/var" failed: File exists (17) rsync: keep_backup failed: "/backup/server/var/lib/rpcbind/rpcbind.file" -> "../server-before-5/var/lib/rpcbind/rpcbind.file": Success (0)

Through several versions up to and including the current 3.0.9 I experience sporadic, repeating (but not predictably) errors of this form: > rsync: make_bak_dir mkdir "/REPO/backup/XXXX-data1-20120727-040453" failed: File exists (17) > rsync: keep_backup failed: "/REPO/backup/XXXX-data1/data1/A182/tb5178/tb5178.hebb/out.TENT_warn.txt" ->

I have users running rsync 3.0.6 on Mac OS 10.5 and 10.6 with the following arguments (for example): rsync -aNHAXx --fileflags --force-change --no-inc-recursive --delete-during --filter="P _Archive*" --filter="P /*" --backup --backup-dir="_Archive_2010_March_07_22-27-43" / /Volumes/Backup I can't seem to figure out how make_bak_dir could be returning this error

here (in keep_backup())? --- backup.c.orig Mon Dec 9 17:02:36 2002 +++ backup.c Mon Dec 9 17:03:50 2002 @@ -273,6 +273,7 @@ /* move to keep tree if a file */ if(!kept) { + make_bak_dir(fname,backup_dir); if (!robust_move (fname, keep_name)) rprintf(FERROR, "keep_backup failed %s -> %s : %s\n", fname, keep_name, strerror(errno)); this reconstructs parent

Hi: Suppose I have the following files on my target volume: /Applications/[45,000 sub files and directories] /Developer/[120,000 sub files and directories] ... (another 8 or so directories with lots of files and sub directories) /usr/ [75,000 sub files and directories] For a total of approximately 500K files and directories. On my source, I have only a handful of items: /Data/ [70 items]

https://bugzilla.samba.org/show_bug.cgi?id=2758 Summary: "File exists" error using options -b and --backup-dir with device files. Product: rsync Version: 2.6.4 Platform: All OS/Version: AIX Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

Hello everybody, this is a reply to the discussion found at: http://comments.gmane.org/gmane.network.rsync.general/22018) I still get this error from time to time, so I suppose it is not fixed in version 3.0.9. Just downloaded the patch and recompiled will test the next days. Is there a bug report for this in bugzilla? Could not find anything. -- Best regards, Chris

When I perform a rsync with backup I get 100's of: make_bak_dir mkdir "/export/giger.back.....eary/java/weka/gui" failed: File exists make_bak_dir mkdir "/export/giger.back....ary/java/weka/gui" failed: File exists make_bak_dir mkdir "/export/giger.back...ary/java/weka/gui" failed: File exists . . . My backup command is: rsync -q --backup

Hello, I use rsync for incrmental backups in the following way: rsync \ $EXCLUDE \ -e ssh \ --archive \ --numeric-ids \ --compress \ --relative \ --one-file-system \ --cvs-exclude \ --delete \ --delete-excluded \ --bwlimit=0 \ --backup \ --suffix='' \ --backup-dir=$BACKUP_ROOT/$BACKUP_HOST/${TODAY} \ $BACKUP_HOST_AND_PATH

In the past there have been discussions about adding a switch to rsync to preserve the atime on files being copied by rsync. I needed this function for a project I'm working on and decided to invent it. I've attached the diffs. Note that this has the limitations describe in previous emails, namely that preserving atime causes ctime to not be preserved. *** Patch follows *** ***

I tried rsync 2.6.1cvs on my FreeBSD 4.X boxes. It dumps core when preserve_hard_links and backup. And SUPPORT_HARD_LINKS is true. rsync -avH --delete --backup --backup-dir=/some/backup/dir \ srchost::dir/ dir/ The core says... ------------------------------------------------------------------------ Program terminated with signal 11, Segmentation fault. #0 0x80536c0 in keep_backup

Hello, I've been porting rsync-3.0.7 to run on UWIN, an AT&T Labs open source project, supporting a Unix environment on Windows. The code configured easily and compiled without any modifications or ifdef's added to the code. The backup test was failing because it didn't create a subdirectory. In tracing the code I realized the problem was in robust_move() in backup.c. UWIN returns

I am try to use rsync from my windows box (under cygwin) to back up "My Documents" on to a debian server (known on my home network as roo.home) running rsyncd from inetd where it is run as root. my rsyncd.conf file sets the gid and uid to user backup.backup thusly:- syslog facility = daemon uid = backup gid = backup hosts allow = 192.168.0.0/24 hosts deny = 0.0.0.0/0 timeout = 600

Hello, I'm new to this and am trying to modify the "backup to a central backup server with 7 day incremental" script from http://samba.anu.edu.au/rsync/examples.html to suit my situation. I have ended up with the script attached below and when running it from command line I get these errors: rsync error: syntax or usage error (code 1) at main.c(726) and a plethora of this >

Moin, I want to use rsysnc to get files from a linux box to a solaris server. root at solaris:/root # which rsync /usr/local/bin/rsync root at solaris:/var/log/r5backup # rsync --version rsync version 3.0.7 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 32-bit timestamps,

All callers of robust_rename() call copy_file() if EXDEV is received. This patch moves the copy_file() call into robust_rename(). Patch Summary: -12 +1 backup.c -15 +2 rsync.c -9 +33 util.c -------------- next part -------------- patchwork diff util.c --- util.c 2004-02-17 09:58:44.000000000 -0500 +++ util.c 2004-02-17 10:21:22.000000000 -0500 @@ -355,16 +355,40 @@

Why does using --delete -b --backup-dir relative/path puts the deleted files in the target folder, while using the full path works as expected? my experimentation... root@feral:/tmp/test (0)>uname -a Linux feral 2.4.22-1.2115.nptlsmp #1 SMP Wed Oct 29 15:30:09 EST 2003 i686 i686 i386 GNU/Linux root@feral:/tmp/test (0)>rsync --version rsync version 2.5.6 protocol version 26

Running rsync 2.4.7pre1, using the --backup-dir option, I just realized today that file ownerships and permissions of backed up files are not preserved. In other words, if rsync moves an obsolete file to the backup dir, it's ownership seems to revert to root:root, and permissions change, as well. We are also using the -a (archive) option, by the way, which should mean "preserve

Hi, My platform is Ubuntu 12.04. The hostname is puppet and this is a Virtual Machine in Vmware 5.0. This is a lab server and it is behind a proxy. I am having a problem with the installer. Any ideas what is going on? root@puppet:/home/rbgonza/puppet/puppet-enterprise-2.8.0-all# ./puppet-enterprise-installer

Local end (receiving): 3.0.2, 3.0.3pre2 Remote end (sending): 2.6.9 Under 3.0.x, rsync sometimes prints an "Invalid argument" error when moving sockets to the backup directory (--backup-dir): rsync: mknod "/backup/machine/../machine-before-4/var/run/audit_events" failed: Invalid argument (22) The problem appears to be that, at least with sockets, keep_backup() is calling