Adjust torrents volume mount to allow hardinking #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The current method of how you mounted the downloads ` ~/data/downloads/torrents:/downloads` means that when an *arr picks up a download it will have to copy the data, leaving a copy in the DL folder until seeding goals are met. This means double space use and excessive disk IO. This is because its a move across file systems from `/downloads` to `/data`. Instead by mounting as `~/data/downloads/torrents:/data/downloads/torrents` then *arr apps and transmission are referencing the same volume and the files are hardlinked into the media library, in an instant operation (instead of copy) and using only 1 x the space.
|
The existing paths would not work out of the box without configuring a remote path map as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current method of how you mounted the downloads
~/data/downloads/torrents:/downloadsmeans that when an *arr picks up a download it will have to copy the data, leaving a copy in the DL folder until seeding goals are met. This means double space use and excessive disk IO. This is because its a move across file systems from/downloadsto/data.Instead by mounting as
~/data/downloads/torrents:/data/downloads/torrentsthen *arr apps and transmission are referencing the same volume and the files are hardlinked into the media library, in an instant operation (instead of copy) and using only 1 x the space.