The real reason was a boring one and seemingly unrelated to that file. I just ran out of disk space. Still though, that’s not exactly a helpful error is it
You must log in or # to comment.
Lot of && in that message. The success reason may not be related to the copy failure reason but to another part of the commands?
Without seeing the command it isn’t really possible to tell.
Funny tangent. I remember windows HRESULTS containing E_SUCCESS (error success) and something along the lines of S_FAILURE (success failure) I’m a little fuzzy on that second one though, so someone else can correct me if I have the wrong name for it.
