Brownz
Dabbler
- Joined
- Sep 5, 2017
- Messages
- 23
I am using sonarr and radarr and have noticed I sometimes very rarely have to to tidyup when it fails to correctly manage the files using the 'Remote Path Mappings'. To my knowledge what Sonarr does is once the download client finishes a download it creates a hardlink between:
- download mount point: /mnt/downloads (source)
- media mount point: /mnt/media (destination).
I couldn't find a method inside sonarr/raddarr gui to manage the hardlinks.
I attempted to manually create hardlink like this:
but I just get this as a response with no hardlink created:
Although creating the hardlink in the same mountpoint works fine.
I found this link, which supports the fact its a mountpoint issue: Hardlink in FreeNAS?
The last post mensions
So how does sonarr/radarr manage to get arround this limitation?
I really dont want to re-download the files again..how can I accomplish this simple task?
- download mount point: /mnt/downloads (source)
- media mount point: /mnt/media (destination).
I couldn't find a method inside sonarr/raddarr gui to manage the hardlinks.
I attempted to manually create hardlink like this:
ln /mnt/download/file-01 /mnt/media/file\ 01
but I just get this as a response with no hardlink created:
ln: /mnt/media/file\ 01 # Cross-device link
Although creating the hardlink in the same mountpoint works fine.
I found this link, which supports the fact its a mountpoint issue: Hardlink in FreeNAS?
The last post mensions
The files locations need to both reside on the same dataset though, and if mounted into a jail need to be using the same mountpoint.
So how does sonarr/radarr manage to get arround this limitation?
I really dont want to re-download the files again..how can I accomplish this simple task?
Last edited: