Timeline for How to copy directories with preserving hardlinks?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 18, 2021 at 22:45 | comment | added | Brian B | MacOS rsync will probably never go above 2.6.9 (without an Apple rewrite). Starting in version 3.0 it went to GPL v3. | |
| Jul 30, 2020 at 17:12 | comment | added | Michael | @Matt duh, i was such a pearhead back in 2018! | |
| Jul 30, 2020 at 14:31 | comment | added | Matt | @Michael You don't need the file list ahead of time for -H to work -- proceeding incrementally is fine. You only need the list of files transferred so far to know when to use a hardlink at the receiving end. | |
| Apr 22, 2018 at 17:05 | comment | added | Michael | @cas I don't see why rsync doesn't think -H requires knowing the entire file list. The fact that it doesn't means -H simply doesn't work as expected in most cases! | |
| Feb 3, 2018 at 0:52 | comment | added | msc | Thank you @cas. The rsync in macOS High Sierra is 2.6.9. I'll see if I can get 3.0+ via MacPorts or some other way. | |
| Feb 2, 2018 at 2:22 | comment | added | cas | Also, while rsync is an incredibly useful too, it isn't always the best tool for every job. These days, I prefer to use ZFS datasets so I can snapshot and zfs send them - I mostly use rsync on non-ZFS filesystems. btrfs has a similar snapshot + send capability. | |
| Feb 2, 2018 at 2:18 | comment | added | cas | From man rsync: Beginning with rsync 3.0.0, the recursive algorithm used is now an incremental scan that uses much less memory than before and begins the transfer after the scanning of the first few directories have been completed. This incremental scan only affects our recursion algorithm, and does not change a non-recursive transfer. It is also only possible when both ends of the transfer are at least version 3.0.0. Note that both --delete-before and --delete-after disable this improved algorithm. | |
| Feb 2, 2018 at 1:57 | comment | added | msc | rsync uses gobs of memory when building its file list. For me after many hours of "Building file list..." it filled up my 16GB of memory and bailed having copied nothing. YMMV. | |
| Jul 31, 2012 at 22:04 | history | edited | cas | CC BY-SA 3.0 | grammatical fix: 'the' should be before 'rsync' |
| Jul 31, 2012 at 22:03 | comment | added | cas | yep, i know. I've been using it for years in my backup scripts. also to move files between filesystems as in your question. | |
| Jul 31, 2012 at 18:16 | comment | added | Grzegorz Wierzowiecki | I've checked - it works. | |
| Jul 30, 2012 at 4:13 | history | answered | cas | CC BY-SA 3.0 |