similar to: Does rsync verify its writes?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You didn't say if you were networking or what features of rsync you are using but if you aren't networking and aren't doing anything fancy you are probably better off with cp -au which is essentially the same as rsync -au except faster. Anyways, smaller reads and writes are usually better handled by the OS's caches than really big

I hope this isn't a FAQ. Per the man page I see ways to control the blocksize for hash comparison reasons, but no way to control it for i/o performance reasons. I'm using rsync to copy folder trees full of large files and I'd like to have control of how much data is read / written at a time. Maybe read 10 MB, write 10 MB, etc. Is there an existing way to do that? == details ==

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

In message <560C79FF.5010302 at sanitarium.net>, Kevin Korb <kmk at sanitarium.net> wrote: >Because you are making two/one. Change to: >rsync -n -v --itemize-changes -checksum -a one/ two/ OK, I tried it with your suggested command line, and yes, that produces rather more substantially useful results. However... Perhaps I am just a bit thick, but I really don't have any

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, > > > >

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.......

In message <560C660F.5000202 at sanitarium.net>, Kevin Korb <kmk at sanitarium.net> wrote: >Just add --itemize-changes and --checksum to what you were doing >before and know that it will take a long time. I'm still not getting to where I need to be. Maybe you can explain what has gone wrong in this very simple example: % mkdir one two % echo hello > one/hello % ln

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]

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,

Kevin Korb <kmk at sanitarium.net>, I thank you greatly for your attempts to educate me, however as we get deeper into discussing more and more different rsync options, I feel that I am actually just getting more confused and frustrated. I've been sitting here, trying all sorts of different combinations and permutations of the various options we've discussed, and that you've

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yes, when it comes to local copies cp is significantly faster than rsync. Without --link-dest there isn't much advantage to using rsync for backups. The only thing you get beyond cp -au is --delete. Also, when it comes to static data like media files I like to keep an md5 file around with checksums for all the files. That way I can easily

How do I transfer just the modification times with rsync? I now the file content is the same but the modification times are different. Is there a way to do this? Every way that I have tried causes the whole file to transfer as well. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

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: >

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,

rsync in daemon mode is very powerful, yet it comes with one big disadvantage: data is sent in plain. The workarounds are not really satisfying: - use VPN - one needs to set up an extra service, not always possible - use stunnel - as above - use SSH - is not as powerful as in daemon mode (i.e. read only access, chroot, easy way of adding/modifying users and modules etc.) Why was encrypted

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

is there a script which analyses rsync output with --itemize-changes ? i.e. i would like to have extended information on number of deleted files, created directories, changed files.... i know rsync 3.1.x is better with this, but it`s still not in centos 5/6/7 and i don`t want to update tons of systems to get extended statistics, so i wonder if anbody did an analyze script to get that information

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.