similar to: Problem with rsync-2.6.8 and -c (checksum)

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

On Fri, 17 Apr 2015 23:45:42 -0400, Kevin Korb wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > So, I am assuming that without --itemize-changes you couldn't tell the > difference between "I am transferring a file" and "I am fixing the > timestamp on a file". > > Even if I am right, you are probably still mis-using --checksum. When

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

Below is a fix for the current problem of checksum offload not working in a NAT''ed network. The cause is the NAT/iptables code incorrectly modifying the TCP/UDP checksum (for the checksum offload case). The original code assumes a valid checksum, which is not the case for checksum offload packets (which has a complimented, partial checksum for the hardware to use). The fix is to

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

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'm trying to understand the point of the --checksum-seed option. As I understand it from a little reading, checksums are not cached over executions of rsync. So...what is the point of fixing the seed? Is this in support of patches which *do* support caching of checksums? I've read about caching these in files and in xaddr. Is there a "best solution" for caching

On Fri, 17 Apr 2015 21:27:56 -0400, Kevin Korb wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Any time rsync wants to do something to a file you don't think it should > be see what --itemize-changes says about it. In fact, -v is almost > entirely useless without --itemize-changes. In fact, if I was in charge > I would make -v include --itemize-changes.

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

On 6/30/07, Wayne Davison <wayned@samba.org> committed: > Added Files: > checksum-xattr.diff > Log Message: > A simple patch that lets rsync use cached checksum values stored in > each file's extended attributes. A perl script is provided to create > and update the values. Wayne, You should be aware of two drawbacks of caching checksums in xattrs: First,

https://bugzilla.samba.org/show_bug.cgi?id=13735 Bug ID: 13735 Summary: Synchronize files when the sending side has newer change times while modification times and sizes are identical on both sides Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW

Hello, I use rsync (3.0.9) to make backups with the link-dest option, so that I keep daily folders, and I only upload the difference. However, when a directory is moved somewhere else in the tree, it is fully re-uploaded. Same thing when files are simply renamed, they are re-uploaded, not linked. First option could be to use --fuzzy twice (migrating to 3.1.0), but I think that it can be very IO

Wayne, I notice that .rsyncsums is starting to look a lot like the index that the git version control system ( http://git.or.cz/ ) uses to determine whether a file has changed since it was last staged for committing. The git index has been heavily used and tested, so you might find it helpful when implementing a checksum cache for rsync. Specifically, it has protection against being fooled when

https://bugzilla.samba.org/show_bug.cgi?id=7936 Summary: Random false checksum mismatches Product: rsync Version: 3.0.7 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: matt at mattmccutchen.net

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 trying to do a backup of several servers which are almost identical. I want to have a "base" directory and one directory by server. The base directory will have only the files which are identical on all the servers, and each server directory will have all of the other files which are not in base directory. So I'm trying to use rsync for : - deleting files which

Hi All, Any inputs on this issue? -- Shedi On Wed, Feb 21, 2024 at 5:12?PM Shreenidhi Shedi < shreenidhi.shedi at broadcom.com> wrote: > Hi All, > > Copying the content from the GH issue as is. > Need your inputs on the same. > FWIW, the coredump files generated in linux have xattr values which are > > 32 bytes. > > https://github.com/WayneD/rsync/issues/569

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

Please CC me directly as i'm not on the list. I have attached a patch against latest CVS (cvs diff -u) that adds the following functionality. I can break it up if you would prefer it in pieces. Comments welcome. o add compare-perms option This creates a new inode for a file even if only the perms have changed. This way if a file outside of destdir is hardlinked to a dentry inside

Hi all ! I am currently trying to find a smart way to long-term-backup my data. I currently do link-dest-updates to an external hdd. However, I am concerned about data corruption in the backup or the original, i.e. corruption of the data inside the files. Thus i am wondering if there is a way to check the integrity of the backups on the external disk. i.e. to avoid data degradation for