So I know this issue has been beaten to death but I just have one question. See forum post here for reference.
My question is why doesn’t Sonarr handle the Win32 IO error properly and treat it as a failure? It’s able to capture the error in trace/debug logging yet it still treats this as a success.
Yes the truncation issue. Hmm OK I guess I hadn’t noticed that the “System.IO.IOException: Win32 IO returned ERROR_GEN_FAILURE” wasn’t related. In my testing it only threw the Win32 IO error when the truncation occurred during the MoveFile. I’ve since cleared my logs and now i’m using NFS as a workaround. =/
If I get a chance I’ll flip back over to CIFS and re-test with trace logging enabled.