similar to: What is the default compression level for local synchronisation?

Searching the 'net showed that rsync asks zlib to use default compression which is equivalent to --compress-level=6 (http://samba.2283325.n4.nabble.com/what-is-the-default-value-for-compress-level-tp2538905.html) but that would not be a good choice for local synchronisation. Should we use --compress-level=0 for local synchronisation? We are using rsync 3.0.9 and 3.1.1.

On Tue, Mar 20, 2018 at 5:49 PM Kevin Korb <kmk at sanitarium.net> wrote: > Nothing there should be preventing incremental indexing. That means it > should start copying as soon as it finds a file that needs to be copied. > Doesn't it tries to create all (empty) directories first? > On 03/20/2018 02:33 PM, Bráulio Bhavamitra wrote: > > > > > > Em seg, 19

OK. Thanks. Where can I find information regarding how to interpret —itemize-changes? The timestamps aren’t changing, so the target must not be storing them, which I have no idea why. The directory I’m writing to is 777. What is the flag to tell rsync to ignore the timestamps? Thanks, Blake On 6/2/16, 6:18 PM, "rsync on behalf of Kevin Korb" <rsync-bounces at lists.samba.org on

Em seg, 19 de mar de 2018 11:34, Kevin Korb via rsync <rsync at lists.samba.org> escreveu: > The performance of rsync with a huge number of files is greatly > determined by every option you are using. So, what is your whole > command line? > rsync -avP /data-old/ /data > > On 03/19/2018 09:05 AM, Bráulio Bhavamitra via rsync wrote: > > Hi all, > > > >

Cool Thanks! Specifically, the timestamps on both <src> and <dest> match for "ls -l" but do not match for "ls -lu" or "ls -lc” The storage is just an regular HDD in a mac pro tower. I can’t imagine why it wouldn’t handle timestamps. Also of note - this problem doesn’t exist for every file, just the vast majority. So, that just makes it more confusing. Yes,

Thanks Kevin! I¹m unclear how to read the ‹itemize-changes output. Can you provide some insight? This is a local transfer from an external drive to an internal drive all attached to one computer. rsync -aPh --itemize-changes -n /Volumes/shuttle_05/2012_79_1_14_1__1199_Workprint /Volumes/3TB_LTO/LT003A/ sending incremental file list >f..t.......

Thank you! I run --times when I use rsync (I actually use the -a flag) but the times do not transfer over and if I run rsync dryrun with -i I can see that it wants to transfer the files because of times. When I run rsync a second time with your suggestion the times do transfer over. I don't know why... B ________________________________________ From: rsync [rsync-bounces at lists.samba.org]

Hi Kevin, I'm not a systems manager so my apologies if I'm a little lost here. I'm an audiovisual conservator/archivist and I use rsync for transferring files, a lot. Yes, I connect to the server and then it shows up as a disk on my desktop and I run rsync between the external drive mounted on my computer and the now mounted server. So, this would be a local copy? And, therefore,

I create a new thread, because the issue is not really the same, but i copy here the thread that made me jump into the list. My issue is not really that it waits before starting copying, but a general performance issue, specially when there are multiple rsync running at the same time. Here is my situation : I have multiple clients (around 20) with users and i want to rsync their home dirs with

> You are missing the point of the checksum. It is a verification that > the file was assembled on the target system correctly. The only > post-transfer checksum that would make any sense locally would be to > make sure that the disk stored the file correctly which would require > a flushing of the cache and a re-reading of the file. Rsync has no > capability to do this

Hi Kevin, I haven't specified --whole-file. After entering an rsync command the terminal always reads "delta-transmission disabled for local transfer or --whole-file" but I assume that is just a standard phrase that always appears. So, if I am running partial (-P) and not using --whole-file or disabling the delta-transmission, why would an incomplete file be deleted and the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Try it without any --delete options. On 03/27/2015 09:31 AM, Aron Rotteveel wrote: > I am now running with --delete --numeric-ids --relative but the > problem still persists. > > -- Best regards / Met vriendelijke groet, > > Aron Rotteveel > > 2015-03-27 14:22 GMT+01:00 Kevin Korb <kmk at sanitarium.net >

Hi Kevin, Thank you very much. I changed my user in the remote machine (su). Then, by trying again with rsync but with no modification in the source folder, I see that file ownership continues the same. Would be possible for rsync to change the ownership in this case (I am not root) ? Thanks, Regards,CJ Em Quinta-feira, 10 de Setembro de 2015 20:01, Kevin Korb <kmk at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Try also removing --delete-excluded. Without those two options there should be no reason for rsync to require gigs of RAM. Well, unless the other system has rsync 2.x. On 03/27/2015 07:29 AM, Aron Rotteveel wrote: > Yes, I removed "--no-inc-recursive", without success. > > -- Best regards / Met vriendelijke groet, > >

for pre 3.0.9 which is still standard in centos7 with recent updates, --stats does neither show number of deleted, nor added files Am 17. Dezember 2016 18:06:56 MEZ, schrieb Kevin Korb <kmk at sanitarium.net>: >--stats has most of that information in it. > >On 12/17/2016 08:01 AM, devzero at web.de wrote: >> is there a script which analyses rsync output with --itemize-changes

Thanks for the reply. The link-dest is different. It is Feb 1 while the source is Feb 2. I tried setting path = /media/external/ for the daemon and using rsync -a -v -i --delete --link-dest=backup-2016-02-01-0100 --password-file=/media/external/scripts/offsite_rsync.pass /media/external/backup/backup-2016-02-02-0100 backup at 192.168.2.102: :offsite/backup So all three (link-dest, source,

Hi Kevin, Thank you very much for the response. Actually, I don't think I need to clean the backup dir defined in --backup-dir=<backup dir>, when the contents has already been deleted in the destination (no exist), it will delete from the backup dir as well in next cycle, correct? Regards, - j On Thu, Feb 4, 2016 at 12:39 PM, Kevin Korb <kmk at sanitarium.net> wrote: >

Before anyone yells at me, yes, you can use rsync's --checksum to detect (and fix) files that are incorrect despite having correct timestamps and sizes. This would mean that a previous rsync had been corrupted not the current one. But it is important to note that this would only be reported to you if you also use --itemize-changes and what to look for (a file with a c but not an s or a t).

What about -c? It seems I'm getting a lot of spurious file transfer candidates when using: -avvznIi --no-o --no-g --no-p It's showing transfers (receive) for many files I know haven't been tampered with. Thanks, -Clint On Tue, Oct 27, 2015 at 7:53 PM, Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > That is correct.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I want to know what your whole command line was so I can understand your results. On 01/23/2016 04:57 PM, dbonde+forum+rsync.lists.samba.org at gmail.com wrote: > On 2016-01-23 22:02, Kevin Korb wrote: >> What was your rsync source and target that made those? > > What do you mean? Filesystem is HFS (Mac OS X). Rsync version is >