Hi list,
I have some questions on how rsync names the temporary files it create
during a file transfer.
It is my understanding that temporary files are name ..ABCDEF,
where "ABCDEF" is a random 6-chars alphanumeric string.
First question: it is correct to say that the random aphanumeric stri
Hi list,
I would like to know if the following rsync's behavior can be
changed/modified.
I noticed that when rsync receive a file for which the local filesystem
already has a symlinks with the same path/name, it _first_ delete the
symlink, _then_ it start the transfer.
I think there are two
Hi all,
any ideas on that?
Thanks.
On 16/03/2016 16:17, Gionatan Danti wrote:
Hi list,
I have some questions on how rsync names the temporary files it create
during a file transfer.
It is my understanding that temporary files are name ..ABCDEF,
where "ABCDEF" is a random 6-chars al
Hi all,
anyone with some ideas? I am missing something?
Thanks.
On 16/03/2016 16:30, Gionatan Danti wrote:
Hi list,
I would like to know if the following rsync's behavior can be
changed/modified.
I noticed that when rsync receive a file for which the local filesystem
already has a sym
Hi list,
some advices on that?
Regards.
On 16/03/2016 16:30, Gionatan Danti wrote:
Hi list,
I would like to know if the following rsync's behavior can be
changed/modified.
I noticed that when rsync receive a file for which the local filesystem
already has a symlinks with the same path
Il 02-01-2019 21:16 Steve Newcomb via rsync ha scritto:
To summarize: while diskrsync is looking like the most suitable
solution known to us, it would still be more convenient, gentler,
kinder, and wiser if the ability to transfer raw block device content
were added to rsync.
Can I suggest you
Hi all,
rsync seems slow to copy large files. The issue is not related to the
transfer itself, which is quite fast, but to the discovery of different
blocks.
For example, transferring a big (multi-GB) file from src (remote) to dst
(local) with "--inplace" (to avoid a whole-file copy on dst) s
Il 2025-07-30 14:26 Hardy via rsync ha scritto:
So NOT using --inplace will save a lot of network transmission at the
cost of local disk copying. Can you not tolerate the temporary disk
space?
Not in this case: for large file transfer (think about 40+ GB), this
would cause excessive load on t
Il 2025-07-30 08:49 Hardy via rsync ha scritto:
Hi Danti,
away from my computer now, so I cannot check, but I suspect the
--inplace to be the culprit. If rsync has to overwrite the file while
transferring, it may not be able to check blocks in the original?
Regards
Hardy
Hi, I tried with a