similar to: --link-dest copying modified files

Hi! I am running rsync 2.6.4 (on Debian sarge) and I am experiencing a strange behaviour. I am trying to create an identical filetree on the same filesystems with the single files being hardlinks to the source like this: rsync -vaH --progress --delete --stats --numeric-ids -x --link-dest=/path/to/filetree/ /path/to/filetree/ /path/to/current/ /path/to is one filesystem. This creates hardlinks

I've got a problem for which the combination of -R and --link-dest doesn't seem to be quite enough---and I may have discovered a few small bugs as well; test cases are below. [And if someone has a scheme for doing this that doesn't involve rsync at all, but works okay, I'm all ears as well---I'm not the first with this problem.] Here's my problem: I unfortunately need to

(I'm not sending this to dirvish@pegasus because I think that this message applies more to rsync's --link-dest option than to just dirvish.) I recently noticed a huge spike in dirvish network usage and traced it to files whose permissions had been changed. (with rsync v2.5.6) I understand and agree that a --link-dest copy of a source file cannot be hardlinked to, but couldn't a

[please Cc: 666024-forwarded at bugs.debian.org on any replies, thanks] Please see the attached Debian bug report, which includes a helpful bug-reproducing shell script; I've confirmed this still happens with 3.0.9. Paul Slootman On Tue 27 Mar 2012, Ian Jackson wrote: > Package: rsync > Version: 3.0.7-2 > > With rsync --link-dest, if two different source files (not hardlinked

I notice that devices are not hardlinked when using the --link-dest option, for instance: rsync -aH --link-dest=../bar/ foo/ baz/ When foo/zero is a device, baz/zero is not a hardlink to bar/zero. How come? $ rsync --version rsync version 2.5.6 protocol version 26 on linux 2.4.x -- Russell Senior ``I have nine fingers; you have ten.'' seniorr@aracnet.com

https://bugzilla.samba.org/show_bug.cgi?id=3175 Summary: devices and --link-dest don't seem to work together Product: rsync Version: 2.6.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

I'm running a mirror of several repositories that are fetched using separate rsync runs. Since some of those repositories are hosting related files, I'm using the hardlink utility[1] in order to save disk space. However, I've noticed an issue that may lead to potential file metadata inconsistencies when using hardlink. Consider the following scenario: - two repositories (rep_a and

https://bugzilla.samba.org/show_bug.cgi?id=13656 Bug ID: 13656 Summary: --link-dest target with symbolic links from different user produces unnecessary error Product: rsync Version: 3.1.3 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 Component:

On Mon, 15 Dec 2003, jw schultz <jw@pegasys.ws> wrote: > OK, first pass on TODO complete. .... > PERFORMANCE ---------------------------------------------------------- .... > Traverse just one directory at a time > > Traverse just one directory at a time. Tridge says it's possible. > > At the moment rsync reads the whole file list into memory at the >

https://bugzilla.samba.org/show_bug.cgi?id=3692 Summary: regression: symlinks are created as hardlinks with -- link-dest Product: rsync Version: 2.6.7 Platform: x86 URL: http://rsync.samba.org OS/Version: FreeBSD Status: NEW Severity: major Priority: P3 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=3175 ------- Additional Comments From foner-rsync-bugzilla@media.mit.edu 2005-10-17 04:36 ------- Created an attachment (id=1518) --> (https://bugzilla.samba.org/attachment.cgi?id=1518&action=view) Transcript of unsuccessful attempts I have other transcripts with me experimenting with all four possibilities of trailing or no trailing slash

On 12/18/2013, 04:00 , lists at benjamindsmith.com wrote: > I may be being presumptuous, and if so, I apologize in advance... > > It sounds to me like you might consider a disk-to-disk backup solution. > I could suggest dirvish, BackupPC, or our own home-rolled rsync-based > solution that works rather well:http://www.effortlessis.com/backupbuddy/ > > Note that with these

Hi, I have to synchronize a directory tree of one machine with a tree on a remote machine. The tree on the remote machine is used read only. In addition I clone the current target tree before each synchronizing using hardlinks to be able to switch back to any previous version if the synchronization failed or if it contained any bad data. This works since 2002 using tar and a perl script. After I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rsync 3.0.9 here. I am using a rsync script like: """ rsync -z --numeric-ids -a -H --inplace --delete --delete-excluded - --stats --progress -v --itemize-changes SOURCE DESTINATION """ I detected the following issue when RSYNCing a bunch of Mercurial repositories. It is very dangerous, because it will corrupt files.

Hi, now it's time to come back to this topic. As supposed, the missing hardlinks where no issue of rsync. I am not sure if pairing aufs (http://aufs.sourceforge.net/) and rsync -RH will catch each and every hardlink compared to a single filesystem, but it seems to work very reliable. I tried mhdfs and aufs. Aufs is faster and very stable (I am on wheezy kernel 3.2). So at last I have my

On 10/02/19 4:50 PM, Robert Moskowitz via dovecot wrote: > I have been thinking, and reading, on how to back up my mailserver. I > have not found any approach that seems ready to use. > > > I have run years without any backup, but would really like to have > something in place.? I figure I can attach a USB drive and backup to > that, then from there rsync to something

https://bugzilla.samba.org/show_bug.cgi?id=10334 Summary: rsync doesn't log hardlink-copies using --link-dest Product: rsync Version: 3.0.9 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: Kontakt at

Hourly I have an rsync job backup /home to /home/backup. I have 24 directories (one for each hour): home.0 ... home.23 Here is the script I am running via cron: #! /usr/local/bin/bash dest=`date +%k | sed 's/ //g'` linkdir=`date -v-1H +%k | sed 's/ //g'` chflags -R noschg /home/backup rm -rf /home/backup/home.$dest rsync -ahHP --numeric-ids --delete --stats --link-dest=../

https://bugzilla.samba.org/show_bug.cgi?id=4793 Summary: link-dest hardlink does not always work well with -o -g -p Product: rsync Version: 2.6.9 Platform: PPC OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi, I detected a silly behaviour of rsync when new hardlinks of already synced files are created: Scenario: There are a local directory and a equal remote directory created by former run of rsync. Create a hardlink from a already existing file (both inside the local directory). If this hardlink has a filename with comes before the original filename when both are sorted in alphabetic order,