From 05059dec6139024f68a59b30851ca8b8189fd256 Mon Sep 17 00:00:00 2001 From: Donald Webster Date: Sat, 8 Aug 2020 19:45:50 -0700 Subject: [PATCH] Add a permissions on destination common problem. --- Downloads-and-Importing.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Downloads-and-Importing.md b/Downloads-and-Importing.md index 1c4c161..b76fb5a 100644 --- a/Downloads-and-Importing.md +++ b/Downloads-and-Importing.md @@ -37,4 +37,7 @@ The download client should download into a temporary-ish folder and Sonarr shoul Sonarr should be setup to use a category so that it only tries to process its own downloads. It is rare that a torrent submitted by sonarr gets added w/o the correct category, but it can happen. If you're adding torrents manually and want sonarr to process them, they'll need to have the correct category. It can be set at any time, since sonarr tries to process downloads every minute. ## Packed torrents -If your torrent is packed in `.rar` files, you'll need to setup extraction. You can typically search your torrent client's name and "unpack" to find a solution. There are some other interesting solutions in this space, like [unpackerr](https://github.com/davidnewhall/unpackerr) and [rarfs](https://sourceforge.net/projects/rarfs/), but they're more complicated. One issue to look out for with packed torrents is that the video file will be copied or hard linked like normal, but it isn't needed since the `.rar` files are seeding. That means if you're using a *copy* setup, the torrent will be consuming double the space. And if you're using a hard link setup, your torrent folder will be a little messier because of the unneeded file. This can be mitigated w/ a [cleanup script](https://gist.github.com/fryfrog/94716e7e27ba38dff57c7631d9f58bed). \ No newline at end of file +If your torrent is packed in `.rar` files, you'll need to setup extraction. You can typically search your torrent client's name and "unpack" to find a solution. There are some other interesting solutions in this space, like [unpackerr](https://github.com/davidnewhall/unpackerr) and [rarfs](https://sourceforge.net/projects/rarfs/), but they're more complicated. One issue to look out for with packed torrents is that the video file will be copied or hard linked like normal, but it isn't needed since the `.rar` files are seeding. That means if you're using a *copy* setup, the torrent will be consuming double the space. And if you're using a hard link setup, your torrent folder will be a little messier because of the unneeded file. This can be mitigated w/ a [cleanup script](https://gist.github.com/fryfrog/94716e7e27ba38dff57c7631d9f58bed). + +## Permissions on the destination +Don't forget to check permissions and ownership of the *destination*. It is easy to get fixated on the download's ownership and permissions and that is *usually* the cause of permissions related issues, but it *could* be the destination as well. Check that the destination folder(s) exist. Check that a destination *file* doesn't already exist or can't be deleted or moved to recycle bin. Check that ownership and permissions allow the downloaded file to be copied, hard linked or moved. \ No newline at end of file