Documentation suggestion (and question)

[gecon]

Hi,
thank you for this great tool.
One suggestion here, related to the documentation (which is also a question).

There are no mention in the docs of hard links handling, which in my opinion is not seldom when transferring hundreds or thousands of GB data (several backup tools use hard links).

For example: Is it safe to add -H in the rsync call?
Adding --delete to rsync is documented. But what about adding -H?

[hjmangalam]

Hi Giannis, I haven't explicitly tested the -H flag with parsyncfp2, but unlike the --delete.. options, it should be handled correctly since there aren't the same fan-out complications as with the delete options. If you try and it appears to fail, I'd certainly be interested in hearing about that failure tho. Harry

…

On Sat, Jun 1, 2024, 12:50 PM Giannis Economou ***@***.***> wrote: Hi, thank you for this great tool. One suggestion here, related to the documentation (which is also a question). There are not any mentions in the docs about hard links handling, which in my opinion is not seldom when transferring a lot of data. For example: Is it safe to add -H in the rsync call? Adding --delete to rsync is documented. But what about adding -H? — Reply to this email directly, view it on GitHub <#19>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASF3Y76MX4VGV22IYGG5ITZFIJY3AVCNFSM6AAAAABIULX3NKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDSMRYG43DONQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[gecon]

Hi Harry, thank you for your prompt reply.

I admit I haven't tried it, yet.

The reason I am wondering especially about hard links, is because I have read the section "Notes about hard links" on https://www.fpart.org/fpsync/
(which also uses fpart)

Quoting the first sentence:

Rsync can detect and replicate hard links with option -H but that will NOT work with fpsync because rsync collects hard links' information on a per-run basis.

Do you think parsyncfp2 is also having the same limitation?

[hjmangalam]

Hi again, Yes, the fsync explanation is both correct & nicely explained. I'll add a similar warning and filter to pfp2 to avoid that situation. Thanks for pointing this out. Harry

…

On Mon, Jun 3, 2024, 4:37 PM Giannis Economou ***@***.***> wrote: Hi Harry, thank you for your prompt reply. I admit I haven't tried it, yet. The reason I am wondering especially about hard links, is because I have read the section "Notes about hard links" on https://www.fpart.org/fpsync/ (which also uses fpart) Quoting the first sentence: Rsync can detect and replicate hard links with option -H but that will NOT work with fpsync because rsync collects hard links' information on a per-run basis. Do you think parsyncfp2 is also having the same limitation? — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASF3Y6OVBQWZ2RDM36RGM3ZFTVZRAVCNFSM6AAAAABIULX3NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBWGI2DENZZGA> . You are receiving this because you commented.Message ID: ***@***.***>