Repository navigation
[FR] Different Hardlink Detection Modes (All/Any/Largest File/Percentage(?)) #1153
Replies: 1 comment
Agent BriefCategory: enhancement Current behavior: Desired behavior: Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Feature scope is a maintainer call — whether this lands as modes on the existing enum field or as a new coverage field decides how far the automations condition surface and its UI grow. |
Uh oh!
There was an error while loading. Please reload this page.
What?
I recently migrated from qbit_manage to the new qui automations for the hardlink check.
"Unfortunately" the qui hardlink check works in a different way than the qbm hardlink check:
qui/pkg/hardlink/hardlink.go
Line 16 in 8b08b87
How?
It would be great (if possible) to have different checking types available for choice, similar to the different hardlink scopes right now (check if any, all or the largest file is hardlinked - maybe even if a specified percentage of files is hardlinked?).
Why?
I run jdupes occasionally as I had some cases of hardlinks not working or breaking in the past, without limitations to specific filetypes, to have a "maximum effect" of hardlinks. Because of that some torrents that share some of the files (especially smaller files in BDMVs) have hardlinks and don't appear as "not hardlinked" as they have for example some 1-2 KiB files linked between each other.
Another advantage could be for larger packs containing many files (not limited to series/seasonpacks) where it might be possible to only have a small portion of files hardlinked, which you might want to have tagged/handled if the amount of existing hardlinks don't justify keeping the whole torrent.
(Example: A friend has 95 torrents with a size >100 GiB each, from which exactly one is managed by the *arrs. The others are manually handled stuff like BDMVs or other content)
All reactions