The network drive became unmounted, but because Unix, that meant I just copied my backups onto my system drive until it was full.
Some days, you just have to ask yourself, <Am I the sort of degenerate who's going to go read the rsync code and see if it properly handles hardlinked directories?>
(The answer is yes. It's not obviously broken at first glance, but I'm not going to go further than that.)
None of the rsync changelogs call out the ability to recognize hardlinked directories. (My source is a Time Machine backup drive.)
Now, maybe it deals with that unusual feature correctly. Maybe the hardlink detection is generic enough that it just works.
The rsync enthusiasts have convinced me to try that way. Let's see if it can correctly handle the bullshit that lies beneath.
Step one: update to latest rsync.
Step two: read man page.
Watch this space for reports of how well it worked in a few days.
In conclusion: it didn't work correctly.
I dunno what happened, but it copied over basically everything from 2015 and 2016, then dropped everything between then and now.
So that sucks.
Question: given a process that has been running for over 48 hours, how long should I allow it to run with the estimated time remaining at five seconds?
Is Steel Ball Run the secret Iron arc?
Does Phantom Blood reference the Phantom that attacks you if you don't sleep?
Will the next Minecraft update include a Battle Tendency?
How does Netherite fit in?
I found the problem.
(The spindle that holds the CDs in place came right off. I was able to put it back on, but... I might need to look into replacing the thing.)
Damn. I started this on Friday and it's still showing 14 hours to go.
I hope it actually works.
Timely advice from _The Who_: