similar to: Deleting modified files

https://bugzilla.samba.org/show_bug.cgi?id=7618 Summary: symlinks and --link-dest Product: rsync Version: 3.0.7 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: the_majkl at seznam.cz QAContact:

Hello, I am noticing inconsistencies when using a trailing slash on the source directories in conjunction with the '--delete' option. In one instance when using a trailing slash files get deleted from subdirectories in the destination tree. In the other instance they don't. I am using rsync 2.5.5. The following are the scenarios: Scenario 1 ---------- *nix(src) ---> *nix(dest)

Patch includes fixes to man page including: - Typos/Spelling - Clarity - Special characters. - Moved around text explaining example. Make sure I didn't confuse the exclude list/file paragraph (line ~961 after applying the patch), I haven't used the feature and the motive of that paragraph is a tad unclear. Hope the patch is helpful. Never had used yodl before. Thanks for rsync. /a

I'm doing a recurring copy from one server to another from the crontab in this fashion: rsync -av -e ssh --delete 10.0.1.18:/dir1/ /dir1 --progress &> /var/log/rsync_backup.log However, rsync is creating the dir /dir1/dir1 on the machine running this job instead of updating the /dir1 folder. According to the rsync man page, this is the correct syntax: rsync -avz foo:src/bar/

Hi I have a problem with rsync and the -c option. I think understand what it does, but I'm not sure, it does it correctly. But then I guess, perhaps I don't understand what it does... :-) I use "rsync version 2.6.8 protocol version 29" I use the following command: /opt/rsync/bin/rsync -av --link-dest=/home/user/backup/old /home/user/source

Hello, I have read through the list of previous issues regarding this issue but haven't been able to resolve mine. I apologize in advance for the long text and am probably doing some simple typo. I have two servers in my setup: *Server 1* Doing rsync with --link-dest daily and working as expected. I'm getting the hard links in the new daily directories. *Server 2* Running rsync daemon

https://bugzilla.samba.org/show_bug.cgi?id=4128 Summary: ignore-times with link-dest behaves unexpected / sematics not clear Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Overview -------- I am trying to use --ignore-times with --link-dest and find that all files are duplicated inappropriately (IMHO). I think it is because --link-dest creates a hard link, which results in the link count, and so Change Time, changing. This requires rsync to create a new inode and duplicate the data just to preserve the ctime. If --ignore-times is not specified, only mtime and the

Hi, I'm having trouble with --compare-dest, to copy only files that differ in content. Here are the commands used thusfar: rsync -av --checksum --delete --progress --stats --compare-dest=../old new/ new_archive rsync -av --checksum --delete --progress --stats --compare-dest=../new old/ old_archive old/ a.txt new/ a.txt Note: both a.txt are the same (except for a different

I am using rsync with --backup --backup-dir to keep copies of files which have changed as part of an incremental backup system. However, if only the timestamp has changed, it creates a copy of the file in --backup-dir, and if thousands of large files have their timestamps changed, this can waste a lot of disk space on something which hasn't really changed. Interestingly, if you use

When using the rsync server without chroot, the --link-dest and --compare-dest options are almost useless. This is because sanitize_paths is called on the link-dest directory, stripping out leading dots and slashes. Thus, the only possiblitiy for a link-dest directory is under the target directory, which is generally not useful. There doesn't seem to be an easy fix. sanitize_paths is

Updated to current cvs without the --exclude-from - patch. This patch allows specifying a --link-dest path similar to --compare-dest except that unchanged files are hard-linked to the --link-dest path instead of producing a sparse tree. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember

Hi all! I've read the manual and google'ed aplenty, but sadly can't figure out this particular issue. Perhaps someone can thwack me with the correct cluestick? I have a number of directories listed under one path in an rsyncd module. I'd like to rsync the contents of some of the directories. Here's essentially what the source filesystem looks like: /home /home/user1

I am working with rsync on Debian, package version 3.0.9-1. I am trying to use rsync --compare-dest to make a delta-copy of a directory. In my case, the mtimes are all unreliable. The data is the same, but the times are all messed up and always will be. I am trying to use --compare-dest with --checksum or --size-only and it does not work. All files are transferred and the delta copy

Hi All, I am writing a backup program for my computer. brief outline is as follows. Running ubuntu 10.04 2 main partitions, / and /home, both ext3. 1 external usb hdd, ext3, mounted to /backups/main. once every couple of days, rsync backs up, using following command, everything worth backing up in / and /home partitions to a folder /backups/main/Full. command: "rsync -vrhRupElog

I have setup rsync to backup another linux computer with the link-dest option and realized storage savings. 1st backup is 31gb, daily backups only take approx 4gb. But when I rsync with link-dest to usb external drive all backups take up 31gb. Following is 1st the one that works and 2nd with no storage savings. Any ideas? Thanks, Frank date>/aeprodbk/bkupdate d=`date +%d` date > $d.log

I noticed that rsync is happy to hard-link a device node from a --link-dest dir even if its mtime differs from that of the source device node and --times is given. Is this behavior expected? It seems to break the rule that a difference in preserved attributes disqualifies a hard link. To see the behavior, run the following as root: mkdir src dest basis mknod src/null c 1 3 sleep 1 mknod

This is a patch to add an --rsync-exclude option to rsync-2.5.6cvs. File names in .rsync- (or .rsync+) are excluded (or included) from the file lists associated with the current directory and all of its subdirectories. This has advantages over --cvs-exclude for backing up large file systems since the .cvsignore files only apply to the current directory: unless the .cvsignore restrictions apply

Hi guys, I've been struggling with getting --link-dest working for a couple of hours now. I'm using rsync 2.6.9 (protocol 29), on Gentoo Linux. For some strange reason, whenever I recreate the source file, even though it's identical to the old source file --link-dest simply does not create the link. Point in case (starting from a blank directory tmp in my home directory):

Hi! It's me again with another --link-dest issue: I am using dirvish (www.dirvish.org) to create daily backup on disk images. dirvish is using rsync with --link-dest pointing to the last good image. This creates images with hardlinks to unmodified files. So far so good. Now I want to create a "current" filetree with hardlinks pointing to the last image. rsync -vaH --delete