Sonarr version (exact version): 2.0.0.4949
Mono version (if Sonarr is not running on Windows): 5.4.0.201
OS: Debian 8
Description of issue:
Sonarr/Radarr falls back to copying content rather than hard-linking due to the use of UnionFS. Ideally hard-linking is preferred to keep I/O usage to a minimum.
mounts:
Google Drive: /mnt/google/media/
Local cache: /data/cloud/media/ - this is a mirror of Google Drive’s directory structure which is used to store processed files.
UnionFS: /mnt/union/ - a combination of the two directories above.
Sonarr/Radarr monitors content within the unionfs mount and as such will rename and then attempt to move the content to this folder. Due to the limitations of UnionFS, hard-linking will fail so it will fallback to copying.
However, if it was moved to the local cache rather than the UnionFS mount, hard-linking would be successful while also showing inside the unionfs mount.
My question is:
Is there any method to have Sonarr & Radarr move content, after a successful rename, to the local cache rather than the unionfs?
Ideally this could be solved with separate folders for monitoring and post-processing destination.
Does anyone else have a similar setup?