Sonarr version (exact version): 3.0.4.1023 Mono version (if Sonarr is not running on Windows): 5.20.1.34 OS: LSIO docker Debug logs: Description of issue:
I have two LSIO Sonarr docker instances that are configured pretty similarly (except for the directory structure). One resides in a native Debian Linux server and hardlinking completed torrent downloads work just fine. The other resides in a Synology NAS and I’m seeing different inodes (so it copies instead of hardlinking even though I have it set to hardlink) for the source and linked files. This happens to both Sonarr and Radarr on the same NAS. Here’s the debug logs for Sonarr:
pretty sure the hardlink only works if both source and destination folders share a common parent path
ie if your download clients are saving to /volume2 and sonarr/radarr store on /volume1 its going to copy, not hardlink
i use a synology nas and hardlinking definitely works. the “transfer” is pretty much instant for a 4gb file when the paths have a common parent. when they didnt you could see it copying the data slowly across.
you may want to delete all the debug logs, as marcus said theyre months old, then set the logging to debug, once you have the data you can set it back to info or whatever level you like - then upload those debug logs. you want to capture a grab and the import of that file.
I posted the same issue in the radarr subreddit and someone suggested to use a common share for the completed downloads folder and the media folder which makes sense. I was using the same volume for both but different they are on different shared folder. /volume1/common/downloads_complete and /volume1/alvin/videos/movies so the docker container thinks they’re two different filesystems. I followed the suggestiok and have yet to test now.
As for debug logging, I keep it enabled all the time so that I won’t have to recreate the issue in cases like this. Is there anything wrong in keeping it enabled?