similar to: This is a bug, right? (--link-dest)

Hi all, I have just migrated my tooling from version 2.6.9 to 3.0.0. Unfortunately my script generated an error message during the execution. Because this command was working perfectly in the previous version I suspect this could be a bug. This is the command that I am executing: rsync -av --link-dest=20080313/ --compare-dest=/data/20080313/ 20080313/ /data/20080314/ It just

Hi all, Recently I do some jobs based on llvm-link tool. I wonder why link '@llvm.global_ctors' into dest file, even it's not used in dest file? And how can I remove it? Thank you all in advance! Fangqing Xilinx Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all, I''ve just rewritten the Puppet introduction from scratch: https://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction I think it''s better, but I''m not convinced it''s a whole heckuva lot better. Comments are very much appreciated, especially if you can recommend a better approach to the document. I tried to organize it how I have been giving

Hello, I'm trying to do backups with rsync through ssh. This is what I wrote yet: src="/vrmd/webserver/" today=`date +%F` #link_dest="root@vm2:/vrmd/admin/backup/web/2004-09-05" link_dest="../2004-09-05" dest="root@vm2:/vrmd/admin/backup/web/$today" rsync -av -e ssh --delete --link-dest=$link_dest $src $dest in 2004-09-05 (on the dest-server) is the

Hi, I've seen the option --link-dest of rsync and this is nearly what I'm searching for. Problem for me is that if remotefile exists the link-dest gets not checked again and I want to be able to pass more than one link-dest to rsync. Has someone an idea for this? Lars

On Mon, Jun 02, 2003 at 03:32:04PM -0700, Michael Rubel wrote: > Hi J.W., > > Please pardon this intrusion on your private address; the rsync list seems > to be down (no messages since yesterday), so I'm forwarding this directly > to you. If you'd rather wait until the list restarts, that's fine too. I'm CCing the list. > > Best regards, > Mike >

Hi all, I'm trying to figure out why a script works when using SSH but not when using the rsync protocol. When I run the following command: rsync -aPh --link-dest=/user/snapshots/rsync_test/last /home/user/rsync_test root at readynas.internal:/user/snapshots/rsync_test/Jan_11_2025 it works perfectly, correctly recognizing the link-dest parameter. However, when I try to run the same command

rsyncd doesn't take unix paths. You must adapt your --link-dest to contend with however the rsycd module is defined in rsyncd.conf. On 1/11/25 9:52 PM, Anthony LaTorre via rsync wrote: > Hi all, > > I'm trying to figure out why a script works when using SSH but not > when using the rsync protocol. When I run the following command: > > rsync -aPh

Hi Kevin, Thanks for your quick response. The rsyncd.conf file looks like: charset = utf-8 [user] path = /c/user comment = "" use chroot = true uid = root gid = root read only = false auth users = admin I'm still confused about how to specify the path. The actual UNIX path is: /c/user/snapshots/rsync_test/last I've tried: --link-dest=snapshots/rsync_test/last

I'm wondering if I can use link-dest to compare rsync to a remote directory. rsync -aCHh --stats --link-dest=akane::backup/ranma.daily.1 / myserver::akane/ranma.daily.0 Something like that? Is it going to work like it does when doing a local rsync with a local link-dest directory? Is it going to chew massive amounts of bandwidth? Is there something else I should be doing

Greetings All, I've been thinking about the current behavior of the --link-dest=DIR option. In the absence of --delete, ALL members of DIR should be linked to the destination (aside from those that are changed). If not, there should at least be a --no-link-dest-delete option. (This latter option might be better to avoid disrupting the behavior of current rsync commands) My rational: This

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

>- --inplace and --append-verify are essentially irrelevant when >- --link-dest is in play. With --link-dest in play the target system >must write an entirely new file even for a change in permissions or >timestamps so any potential benefit by these options are out the >window from the start. The only thing they can do is add the >possibility of incomplete or corrupt copies on

On Sat 11 Jan 2025, Anthony LaTorre via rsync wrote: > Thanks for your quick response. The rsyncd.conf file looks like: > > charset = utf-8 > [user] > path = /c/user > comment = "" > use chroot = true Note the chroot... So "/" equals /c/user > uid = root > gid = root > read only = false > auth users = admin > > I'm

samba-bugs at samba.org wrote: > https://bugzilla.samba.org/show_bug.cgi?id=10637 > > --- Comment #1 from Karl O. Pinc <kop at meme.com> 2014-05-28 19:05:04 UTC --- > Yum is also rsync happy. That's where our --link-dest backups always break due > to too many hard links. ---------- What would be "too many"? -- a few million? I have files in a test setup that

https://bugzilla.samba.org/show_bug.cgi?id=7289 Summary: --link-dest seen as unknown option Product: rsync Version: 3.0.7 Platform: x64 OS/Version: Linux Status: NEW Severity: blocker Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: pjh at lowell.edu

Hi, I can't manage to get rsync's --link-dest option working. Here is a step by step script which doesn't produce the good results. # create test dir mkdir testrsync cd testrsync mkdir orig echo "abcd" > orig/testfile # create a mirror rsync -apog orig/ mirror/ # create another mirror using link-dest rsync -apog --link-dest=mirror/ orig/ mirror2/ # look at inodes ls

Hi, I am using --link-dest for my rotating backups. Noticing the "--detect-renamed-lax" patch to rsync 3.0.0. I was hoping to make use of the --detect-moved. Unfortunately, "--detect-moved" does not seem to recognize the --linkdest option. A moved file is getting transferred again and a new file is created at the receiving end instead of linking to the moved

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

I can use --link-dest multiple times for backups so that files affected by a backup-delete-backup-replace-backup scenario get linked. It works well. However, consider this scenario: backup-modify-backup-undo-backup. We have * backup 1 contains file 'a' * backup 2 contains file 'a' ( with modified content) * backup 3 contains file 'a' However, the file 'a' in