similar to: --partial not working?

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

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,

Partial means don't delete the incomplete file. The file is being transferred because it doesn't match. But rsync does delta-transfers so it won't actually transfer the parts that match. It will just verify that they do match. Unless of course --whole-file. On 06/24/2016 11:47 AM, McDowell, Blake wrote: > Hello, > > > > I’m running rsync -avPhi to move large

If you are doing a local only copy (rsync isn't networking) then --whole-file is forced. There is no benefit of reading and checksumming files to reduce network transfer when there is no network transfer. You said you were moving data to a remote server so I assume you are using a network mount of some kind to make it a local copy instead of letting rsync do the networking. Anyways, if

Again, --partial only means don't delete the incomplete file if rsync is aborted. Normally rsync will delete the incomplete file so you don't have bogus files laying around. When you rsync to or from a network mount to rsync that is a local copy. To use rsync over the network either your source or your target would be hostname:/path (for rsync over ssh) or hostname::module (for an

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]

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

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

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, At my work we use rsync to move files between drives and to LTO among other things. I'm having an issue using rsync to move material between and external drive and an internal drive. We run "rsync -avvPh <src> <dest>" and most of the files keep writing every time I run this. It appears that the modification times are not being carried through to the destination

Hi Steven, Yes, both file systems are the same. rsync -nri --modify-window=1 <src> <dest> Gives me the following for most files >f..T....... 2015_167_1_1__Boy_What_A_Girl_R2/2015_167_1_1__Boy_What_A_Girl__UHD_DPX_R2/ BWAG_R2_00138428.dpx Although a few have >f..T......n 2015_167_1_1__Boy_What_A_Girl_R2/2015_167_1_1__Boy_What_A_Girl__UHD_DPX_R2/ BWAG_R2_00135909.dpx

On Fri 24 Jun 2016, Kevin Korb wrote: > Again, --partial only means don't delete the incomplete file if rsync is > aborted. Normally rsync will delete the incomplete file so you don't > have bogus files laying around. > > When you rsync to or from a network mount to rsync that is a local copy. > To use rsync over the network either your source or your target would

I am trying to figure out what happens in the following scenario: I use rsync to copy files from hostA:/dir1 to hostB:/dir1 with the command (from hostB) rsync -abvt --delete-after --suffix=~ hostA:/dir1 /dir1 So if fileA exists already on both boxes (it has previously been rsynce-d) and fileA changes on hostA. rsync starts from hostB, fileA starts transfer. If the transfer aborts before it

Hello, We have our mac connected to a SAN via 10Gbe fiber network. Being thunderbolt model macs with no PCI slots we are using external boxes (Sonnet, ATTO) to interface between the thunderbolt and fiber connections. When using rsync -avvPhi we get speeds of approx 110MB/s but with a simple drag-and-drop we get speeds of approx 620MB/s. BIG difference. We get the same speeds (roughly)

I am backing up a LARGE data set, over a very unstable internet connection. I NEED to --delay-updates, because I do a flash cut-over once everything has transferred. Yes I know --copy-dest does this, but if the connection breaks, anything that's already made it over gets put into place (not what I want), I need it to go from beginning to end, And then I handle the files seperately. If I

Rsync has no memory of what other instances of rsync have done in the past. An existing file with a different name is of no interest to it unless --delete in which case it would be deleted. Maybe what you really want is --partial-dir? On 6/7/23 16:17, Lacey, Nathan wrote: > I'm suggesting a partial file that isn't hidden is worse. > Because any other app looking at the file

This is a clone from https://github.com/WayneD/rsync/issues/484 run rsync with --progress --size-only --partial (version 3.1.2) also tested/built current master ( 3.3.0pre1-5-g6f3c5ecc ) everything works fine unless I interrupt a transfer ( ctrl c ) I would expect to see the incomplete, temporary, hidden file present on the remote machine. So that when I call rsync again, it could just pick up

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

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