search for: thincopy

Hi everyone :) I'm professionally and seriously working with extended filesystem attributes (xattrs) for search/retrieval of data. I am making a "thincopy" of large data trees, like this: `$ cp --attributes-only --preserve=all $(SOURCE) $(TARGET)` Is there a way to do this with rsync? I'm asking, because I'd like to keep that thin-copy in-sync (including xattrs). Such a thincopy has proven immediately useful as "instant metada...

Dear Roland, On 12/10/24 21:15, Roland Kletzing wrote: > hello, > that sounds interesting - just one question:? what about file size? is > it always zero or is it set to the original size and the file contents > are empty ? The filesize (IMO) should stay 0 bytes, since the file actually /is/ empty. I believe forging the filesize number in the filesystem to its source (original) size

Hello everyone :) I'd like to follow up on this thread of mine, if that's okay? Is there anything I could do to get the feature functionality of "using rsync to create a thin (attributes-only) copy" upstream on the long term? Could I talk to a developer, for hire? I'm really professionally interested in such a feature, as it would greatly make our lives in the

Oh, and since the shell instructions below are idempotent, you could put them into a script and then execute this from the tippety top of your file tree after every transfer, not caring which files are new or modified: find . -exec <script-name> {} \; My use of the option is not idempotent though, so I need a more elaborate script (which also handles other things). I hope you're not

Actually... I have made an extremely small and simple patch implementing an option --time-only, and I have made a pull request for it: https://github.com/RsyncProject/rsync/pull/719 It allows you to truncate your local files after transfer. Outside of rsync, you must then truncate the file to zero size, then set the time stamp back to the original time. On the next run, the file will not be