Sonarr version: v2.0.0.5163
Mono version: 5.12.0.226 (tarball Thu May 3 09:48:32 UTC 2018)
OS: Docker on Ubuntu, using image linuxserver/sonarr
Debug logs: https://pastebin.com/eJLN6Mad
Description of issue:
My setup is in two parts:
- a server (with SSD) running Docker, hosting Sonarr via a container and its config/data via some volumes
- a NAS (with a RAID5 of HDDs), hosting my media files
TL;DR : Sonarr UI freezes during file copy, which is long. Is not Sonarr multithreaded so UI can still respond during copy ? Is there a way to make an “actual file move” instead of “copy then delete” ?
My problem is whenever a download is finished (and Sonarr moves it from the downloads folder to the media collection folder), the Web UI becomes unresponsive for the whole duration of the file copy. As soon as the copy is finished, the Web UI is available again.
In my perfect setup, download and media folders are both on the NAS. I tried different combinations, putting the download folder either on the Server or the NAS, but nothing helped.
From my understanding, the file “move” would actually be a “copy” then “delete”, which seems the best option from a safe point of view, where the file move would failed, and could be tried again. And I guess that during this copy then delete, the sole process of Sonarr being working, nothing can answer my requests from the WebUI.
I’m currently in the combination giving me the fastest possible copy, downloading on the my server’s SSD, then copying the file to the NAS RAID5 when finished. NAS to NAS copy is being ridiculously slow.
Is there anything i missed making a simple file move available instead of the safe “copy then delete” ?
Is this normal than the UI freezes during the file copy ?
Thank you for responses.