similar to: Error code 23, delete failed, error 0

Regarding "rsync error code 23" could the below "delete_file: ...file exist" failures cause the error code 23? Or, how can I resolve this as these are the only errors I see in the log files. Thank you! START Tue Aug 26 11:10:12 PDT 2008 /home/filerep/bin/rsync -e /var/openssh/bin/ssh --archive --stats --timeout 3600 fmttcesrv1::tce_data

I have what I believe to be a bug in the behavior of the current (2.6.4) version of rsync. While trying to upgrade from version 2.5.2 to the current version (for security concerns), I noticed the following difference in behavior between the two versions which is preventing the upgrade: If you have a directory tree on the target such as the following: dir/pdf/file1.pdf dir/pdf/file2.pdf

Hi, sorry if this is old stuff, but I did my best to look first... Have been getting errors along these lines: mv mydir mdir.2002 ln -s mydir.2002 mydir Then update mirror with rsync -av --delete-after. Without --delete-after, no problem, with --delete-after, get a code 23. The attached shell script will recreate the error (on my machine, at any rate). Just run it from a clean directory.

https://bugzilla.samba.org/show_bug.cgi?id=5091 Summary: Incremental-recursive, list-only "rsync --delete" tries to clean out working dir Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

Hello list. I've got following: rsync: opendir "client05" (in Profili) failed: Permission denied (13) rsync: delete_file: rmdir(client02/SendTo) failed: Permission denied (13) Am I correct if I say that the "opendir" is related to the source I'm trying to rsync, but the "delete_file" is related to the destination? Flavio Boniforti PIRAMIDE INFORMATICA

Hello, I'm backing up a file server using rsync from a cron job, which recently started to give me errors like: delete_file: rmdir "/some/path" failed: Directory not empty symlink "/some/path" -> "/some/other/path" failed: File exists Looking at the involved files and directories, it looks like the user decided to replace a directory with a symlink, but

https://bugzilla.samba.org/show_bug.cgi?id=3935 Summary: replacing a full directory with symlink with --delete- after produces cryptic message Product: rsync Version: 2.6.6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

I'm trying to switch to using rsync for updating a huge software library containing binaries, text files, symlinks, and so on. We've been using something homegrown which I'm not that happy with - it's a perl script that systems cp and chmod and such. The problem I'm seeing is: target computer: directories ctime-5 and ctime-5b3 are distinct directories source computer:

Anyone here run rsync on a Win32 platform? I know, I'm a glutton for pain. Anyway, I'm using 'cwrsync' on one system to copy files from a local drive (F:) to a mapped (network) drive (Y:). The problem I'm having is with that infamous 'Network Trash Folder'. I can't get it to ignore it on the remote (mapped) drive, and it doesn't exist on the local drive.

Hi, How about adding now option '--backup-only' that means making backups only and don't change any destination files? (I posted similar patch a month ago, but the patch was made for nightly snapshot of 20020808, which was tooo old! Laugh at me...) I want to use rsync with LVM snapshot to make incremental backups like below: 1) Make LVM snapshot of file system and mount it.

I've gotten several different errors with rsync. Maybe someone can help me. 1. rsync -azSH --stats --delete-after /export/home remote:/export/home/bkup delete_file: rmdir(home/greg/vnmrsys) : File exists rsync: symlink "home/greg/vnmrsys" -> "/export/home/vnmrsys": File exists unexpected tag 91 rsync error: error in rsync protocol data stream (code 12) at io.c(298) 2.

Full_Name: Steffen Version: 2-5-0 OS: Windows Submission from: (NULL) (192.124.243.162) Hi, the R CMD build script is using if($WINDOWS) { ## workaround for paths in Cygwin tar $filepath =~ s+^([A-Za-z]):+/cygdrive/\1+; } which does not work if the build environment is a MINGW. I have added the patch below, Yours, Steffen $ diff -u build build.orig --- build

Please see the included debian bug report, where during a local transfer rsync (3.0.3) follows a symlink in the destination to delete a file in the source tree. At least 3.0.5 works correctly in this regard; however I can't find a changelog entry that's directly related to this. Would it be possible to extract the diff that fixes this so that the 3.0.3 version in debian stable might be

Hi all, I have rsync'ed directory /rootdir/dirdir/ from Server1 to Server2, using cmd on Server2 "rsync Server1:/rootdir/dirdir -avz /rootdir/dirdir". There were some sub-directories from Server1 got updated to become the symbolic links. For example, directory /rootdir/dirdir/subdir1/ now becomes the symbolic link /rootdir/dirdir/subdir1 pointing to the new created directory

Good day, all, I'm using rsync 2.5.4 and a statically linked version of 2.5.5 to back up my main system to a backup drive (See rsync-backup at http://www.stearns.org/rsync-backup/ ). First, I made a full backup of the system. Then, on the main system, I merged the articles in techdocs to another directory called articles, removed the techdocs directory and made it a symlink to the

Hi I'm running rsync 2.5.6 protocol version 26 on solaris 8. I have a local software RAID array, plus a mounted netapp fileserver, and am looking to replicate the contents of the netapp mount on the RAID array. I run a cronjob each night, with lines like :- /usr/local/sbin/rsync -ar /netapp/all/projects /backup/vol0/ >> /tmp/rsync_log.txt 2>&1 Looking at the log files, I get

https://bugzilla.samba.org/show_bug.cgi?id=2409 Summary: rsync doesn't handle directories changing into symlinks well Product: rsync Version: 2.6.3 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hello, I think I found a bug in rsync. I checked the TODO and the issues, but I didn't find any reference to it. It seems, that rsync goofes up, if you rename a directory and then create a symlink with the old name to the new location. Below is a simple example how to do it. ------------------------------------------------------------------------------ [ptriller] elmore:~/test > ls

On Fri, Dec 16, 2016 at 10:17:21AM -0800, Glenn E. Bailey III wrote: > This is a base install. If you deploy an instance in ec2 or GCE (ec2 > you can do the free tier) it's easily repeatable. Even on a RHEL 7.3 > instance. Note you'll need to allow root and password logins via SSH > before attempting. I can confirm this. The culprit? NetworkManager has /home open. I

R developers, I've been happily building packages, under windows, for some time now and upgraded to R 2.1.0 and now when I attempt to build a package, I get the following errors... C:\conifers>rcmd build Rconifers * checking for file 'Rconifers/DESCRIPTION' ... OK * preparing 'Rconifers': * checking DESCRIPTION meta-information ... OK * cleaning src * checking whether