New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import not creating hardlinks as expected #2129
Comments
Did you run |
Ha, silly mistake on my part. I use mergerfs which has it's own way of dealing with hardlinks, but the issue was I wasn't exposing the entire data pool to sonarr, only certain folders so mergerfs couldn't do it's magic inside the container properly. Got it working now :) sorry about that. |
How did you implement this fix @jtpavlock ? |
@chriswiduta mounted all of my data drives to the docker container (in my case I had them under |
@jtpavlock are you using the linuxserver/sonarr container? I am running into this hardlinking issue on my system (also using MergerFS/containers for everything) I am unsure as to how you go about providing this container only one mount point and having the correct downloads/tv folders selected? |
@jonatronnn Maybe this will help, I use docker compose and these are the volumes that I mount
I then select the proper folders with data/ within sonarr itself |
Brilliant, thanks I'll give that a go. What create polices/run options do you use with MergerFS? I did a bit of reading that indcated using a non-path preserving create policy and ignorepponrename=true would help when using hardlinks. |
|
Up and running with what seem to be working hardlinks with my Deluge/Sonarr containers, thanks very much for the information! |
With the create hardlinks feature on, sonarr is still copying files instead of hardlinking them (as shown by the number of links in ls -l).
Now, if I manually hardlink using the same directory set
ln /downloads/example_file /tv/season/example_file
it works as expected and creates the hardlink.
I tried to look at log files, but did not see anything related to importing.
Running version 2.0.0.4949 on Debian under docker.
The text was updated successfully, but these errors were encountered: