similar to: [Bug 9167] New: --dry-run --stats --link-dest provides incorrect stats

https://bugzilla.samba.org/show_bug.cgi?id=10238 Summary: --dry-run does not change directory, causes --link-dest failure on symlinks Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at

I am trying to use rsync for making snapshots, sharing hardlinks at the destination using the --link-dest option. In conjunction with this, I would like for --dry-run to report some reliable-ish number for how much space it is going to consume at the destination so that I can arrange to free such space prior the launching rsync "for effect". Right now, that isn't working: #

https://bugzilla.samba.org/show_bug.cgi?id=5050 Summary: rsync tries to --copy-dest in --dry-run mode Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: hashproduct+rsync@gmail.com

Full updated EL6: Does someone have the same behaviour, unstable eth interface (tg3/no dhcp)? Jan 19 18:01:46 ane kernel: tg3 0000:04:00.0: eth0: Link is up at 1000 Mbps, full duplex Jan 19 18:01:46 ane kernel: tg3 0000:04:00.0: eth0: Flow control is on for TX and on for RX Jan 19 18:01:46 ane kernel: tg3 0000:04:00.0: eth0: EEE is enabled Jan 19 18:01:46 ane NetworkManager[1735]: <info>

https://bugzilla.samba.org/show_bug.cgi?id=12036 Bug ID: 12036 Summary: Multiple --link-dest, --copy-dest, or --compare-dest flags produce incorrect behavior Product: rsync Version: 3.1.2 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:

[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

https://bugzilla.samba.org/show_bug.cgi?id=3693 Summary: rsync can use same --link-dest file several times, leading to incorrect hard links Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

Alright guys, you're my last hope. Currently I am trying to create a rotating backup system. I have a remote server which I've patched to work with the -E option. Anyhow, the remote server has the backup and I'm trying to use --link-dest against it. Here is the command I'm running. sudo rsync --dry-run -e 'ssh -l root' --delete -auE \ --link-dest=../backup.0 \

https://bugzilla.samba.org/show_bug.cgi?id=2390 Summary: some dry run stats inaccurate Product: rsync Version: 2.6.4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: woodd@deshaw.com QAContact:

https://bugzilla.samba.org/show_bug.cgi?id=2390 ------- Additional Comments From woodd@deshaw.com 2005-02-24 17:21 ------- Created an attachment (id=980) --> (https://bugzilla.samba.org/attachment.cgi?id=980&action=view) Proposed sender.c / receiver.c patch -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: -------

I've identified a situation where the combination of --fuzzy --fuzzy (yes: two of them) and --link-dest is not behaving as I'd expect. I'm first wondering if my expectation is wrong. Assuming that it is not, then I'm wondering how best to figure out the problem. The double use of --fuzzy is based upon https://bugzilla.samba.org/ show_bug.cgi?id=4056 which should be present on

Folks, Thinking again about the issue of changed attributes for a file in source that is identical in content to a file in destination that is hard linked get propagated to the --link-dest directories I would like to suggest a new flag, (perhaps called something like --preserve-linked-attributes), to allow callers to get the behaviour that is needed to allow the use of recycled

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If it seeing the files as new then I agree that stat won't help. It might have explained some other itemize output. Since it is seeing the files as new then they must not be where it is looking. Meaning that your link-dest parameter must not be appropriate for your target. On 01/10/2015 08:49 PM, Clint Olsen wrote: > On Sat Jan 10 2015 at

Il 25/07/2012 10:07, Eli Friedman ha scritto: > On Wed, Jul 25, 2012 at 12:48 AM, Michele Scandale > <michele.scandale at gmail.com> wrote: >> Dear all, >> >> I'm working on an exploratory backend on llvm. In the instruction set I'm using >> I have an instruction (called DECJNZ) that decrements a register and, if the >> decremented value is not

On Sat Jan 10 2015 at 5:21:33 AM Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > What does --itemize-changes say about that file? Try using the stat > command on the various copies of it to see what is different about them. > In my original message, I stated I used --itemize-changes, and I reported the following: >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What does --itemize-changes say about that file? Try using the stat command on the various copies of it to see what is different about them. On 01/09/2015 09:42 PM, Clint Olsen wrote: > Hi: > > I've been using rsync for a couple years now. Unfortunately, I've > made some changes on both ends, so it's unclear what could be

Hi: I've been using rsync for a couple years now. Unfortunately, I've made some changes on both ends, so it's unclear what could be the culprit. I make extensive use of --link-dest to provide a cheap "Time Machine"-like backup for a Windows machine. Source: Windows 7 running Cygwin (CYGWIN_NT-6.1 sith 1.7.33-2(0.280/5/3) 2014-11-13 15:47 x86_64 Cygwin) Destination: Synology

I'm currently using rsync and --link-dest to give me something like a poor-man's incremental snapshot to disk. But I really only want to generate a new backup if rsync detects differences, otherwise I don't need a new backup. Currently I do something like this: rsync -a --delete --link-dest=../backup.previous/ source/ backup.next/ diff -r backup.previous backup.next && rm

https://bugzilla.samba.org/show_bug.cgi?id=5263 Summary: failure to report deleted files with link-dest Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: 14709c93@mailinator.com

On Wed, Jul 25, 2012 at 12:48 AM, Michele Scandale <michele.scandale at gmail.com> wrote: > Dear all, > > I'm working on an exploratory backend on llvm. In the instruction set I'm using > I have an instruction (called DECJNZ) that decrements a register and, if the > decremented value is not zero, jumps (with a relative jump) to a given offset. > > I've