-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
[Bug]: Torrents that were hardlinked via cross-seed aren't being tagged as noHL #363
Comments
ls -lha showing that the files are not hard linked? cross seed data would symlink or hardlink them and only hardlink is supported with QBm. It's expected for cross-seed data hardlinked episodes to well, be hardlinked |
Yes there are hard links but according to FR #291 i was of the understanding that if there are no hard links outside of the root dir, which there aren’t, then it should be marked as noHL |
Again please provide the information requested. stat with the ionodes from the individual episodes in client, the season pack in client, and the library episodes would confirm. it is 100% possible and likely that the season pack and individual episodes are both hardlinked to the to the library. |
Thank you for your reply. I appreciate your help. Would you please be able to tell me step by step on how to do this? |
I've encountered a similar issue to this today, and wondered if you can check something. The torrents you're having the issue with, are they all ones where the torrent content is in a subfolder? I've found today that torrents where the content is in a subfolder (or subfolders) do not get flagged as noHL. I discovered this when manually adding a torrent to a new category (correctly added to qbm too), which then got data-match cross-seeded, and the noHL wasn't picked up. |
Hello! Running with trace logging would help identify the root cause of why the torrent was not selected as NoHL. It provides a lot more details so please try that and post the results for the torrent. Since the logs can be quite excessive make sure to post the log only for the specific torrent hash. |
Trace logs: https://privatebin.net/?e2efb1107898c945#BR6v5SkrJBDzH8Q5nfhpof7nhorg1A5SvXHyQDvegV3M (let me know if that's not the right section) |
Unfortunately I’m unable to give the trace logs and inode info due to lack of knowledge on how to do so. I can however tell you that it was a season folder that was then data matched as single episodes and placed into the cross-seed-data folder. All of this folders are in the main directory for downloads that qbitmanage sees. They don’t appear elsewhere appreciate your logs and such and hopefully we can get to the bottom of it. It’s not such a massive problem because for me the main series folder is marked as noHL and then when that is removed, the single episodes are then marked noHL |
For trace logs, you can set the container variable |
ok i have enabled trace logging but not sure what part you would like out of it. Do i need to delete and re add the torrents so they are scanned? |
No - just re-run qbitmanage with trace logging, then have a look at the output and just share the section(s) relating to a torrent you'd expect to be marked noHL but isn't. |
ok so i can only apologise for how dumb i might be but I went into the container setup with unraid and set the log level to debug. Then restarted the container and check the log files in /qbit_manage/logs/activity.log and there doesn't seem to be anything different or anywhere i can find the specific torrent file so either i've done it wrong or i'm looking in the wrong place for the logs |
You'll know it's worked as you'll see lines like this:
...i.e., they have You can get the torrent hash by clicking the torrent in qbit, then under the General tab you'll see it. Search your trace logs for that hash, and you'll find the relevant sections. |
New logs (with longer expiry) here: https://privatebin.net/?8169c634f976c536#KSGvG85R8YzjptsAMyzJmPh1PtRLKV3TpuzRtNaVMdL |
Hi @yammes08 , I notice in the trace logs |
@yammes08 can you also share your config? Is |
@yammes08 , can you update to the latest develop and rerun with trace logs? I think I might have fixed the issue |
Hey @bobokun
I couldn't find either of those things in the logs
Config here: https://privatebin.net/?aa6eb8491ed36e4b#G3ZVhLctGuttrMFshk9kAN3t8Ku9PtQghK3MHf7cUCyw
Updated to latest develop, still seems to be the same issue. New logs: https://privatebin.net/?cbc816f4fc1c50af#54aYKnM6Ybb9BdsbJ2UEJqmRCjhxdh4nq5TZv5kSezEi |
Hold on, I don't think my container updated properly. Re-running. |
OK, I'm seeing this is now fixed! 🤘
|
@removinggoose - perhaps you could update to develop and re-run - see if this is fixed for you too? |
Seems to have done the trick. Thanks |
How often do you have qbit manage run? I'm noticing torrents be given share limits prior to them being hard linked and therefore the share limits stay after the torrent is hard linked. Is there a way around this other than reducing time to minimise likelihood of occurring? |
Share limits should adjust on the next run if they were applied prior to being hard linked. If not it's probably a config issue where the priority needs to be adjusted. |
Sorry to sort of change the subject of the thread. I can start a new discussion if needed. Here is the part of the config that describes the hard links. I'm not sure what priorities do exactly and how to configure it so that it doesn't tag until complete.
|
Priority is clear
you also do not have a default share limit as the docs and config say is needed thus as soon as any share limit group is added for noHL they can and will never have any other groups applied as they match nothing else. your share one tagged noHL your share limits will never ever be replaced because you haven't told QBm to do so |
That solves it. Silly me. Thanks for the help |
Describe the Bug
According to FR #291 , hard links that exist inside the root folder are supposed to be ignored and therefore torrents can still be tagged with noHL if there are none outside the root dir. Perhaps my config is wrong but I am still getting torrents that should be tagged not being tagged because of cross-seed.
An example is a torrent for Chicago Fire Season 9.
This torrent is no hard-linked to my media folder but individual episodes have been hard-linked by cross-seed to the folder "cross-seed-data"
The original full season pack has then not been tagged as noHL.
Config
Logs
https://gist.github.com/removinggoose/43f9b91800fbc96b916d598a57e5bf54
Screenshots
Installation
Unraid
Version Number
4.0.2
What branch are you on?
master
The text was updated successfully, but these errors were encountered: