|
It seems to me the most likely case might be a disk error that is not getting flagged properly. This absolutely should have thrown an error, and if I somehow missed that error in a log or failed copy status, it should be attempting the copy again each time it's scheduled, until it's done right, or keep throwing errors so I notice eventually.
|