Re: Per file Log output to understand hard-link decision

2023-05-14 Thread Hardy via rsync
Don't know if this is enough for you, but it may help at least a bit to hunt down your problem. There is a flag -i From man rsync --itemize-changes, -ioutput a change-summary for all updates this gives either a "." for no change, or a letter code for each change in "data, time, size"

Re: Per file Log output to understand hard-link decision

2023-05-14 Thread Kevin Korb via rsync
The only way I know of to determine this behavior is to use the --link-dest option in rsync OR use the much older cp -al then rsync over top of it method. With --link-dest a change in the file's metadata causes rsync to duplicate the file in order to store both versions of the metadata. With

Per file Log output to understand hard-link decision

2023-05-14 Thread c.buhtz--- via rsync
Hello, I know it is a often discussed topic how rsync decide about using hardlinks or copy a file. Even if content is unchanged problems are often file permissions and owner ships. I know that. Is it possible to configure rsync that way that it logs for each file its decision about using a