Repository navigation
FR: Cross-instance HARDLINK_SCOPE #1805
Closed
skler1
started this conversation in
Feature Requests, Ideas
Replies: 4 comments 3 replies
|
Can you not combine the two conditions to achieve what you are looking for? Edit: So I think after reading your other items I have a better grasp. So your saying you want to know if the same data/content path is being used to x-seed on a different instance or rather any instance? |
3 replies
0 replies
|
@skler1 if you want to test this I'd appreciate some feedback. ghcr.io/autobrr/qui:pr-1810 |
0 replies
|
Merged to develop, will be in the next release. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem / Context
Currently,
HARDLINK_SCOPEin qui's automation engine works per-instance. When qui builds the hardlink index, it callsLstat()on every file of every torrent within a single qBittorrent instance. The three possible values are:none→ no hardlinks detectedtorrents_only→ hardlinks exist within that instance's download setoutside_qbittorrent→ hardlinks to files outside qBittorrentThis works correctly as long as all torrents sharing the same underlying files live in the same qBittorrent instance. It breaks down when torrents sharing the same underlying files (e.g. a download and its cross-seeds) are spread across multiple qBittorrent instances. In that scenario,
instance Ahas no visibility into the hardlinks held byinstance B: the files may havenlink > 1at the filesystem level, but since those links belong to torrents on a different instance, qui cannot associate them with any known torrent. As a result, the scope is reported as
outside_qbittorrent, causing automations to work incorrectly.Use case
A common automation pattern is to tag torrents with
noHLwhenHARDLINK_SCOPE != outside_qbittorrent, then delete those torrents after a seeding period. If the scope doesn't cross instance boundaries, the tag is applied incorrectly to torrents that do have hardlinks on other instances, potentially causing unwanted deletions.Proposed solution
Add a new scope value:
outside_instances, hardlinks exist, but only toward torrents managed by any configured qBittorrent instance, with no links outside of qBittorrent instances (e.g. no media library copy).This fills enables accurate
noHLdetection in multi-instance setups. It would work similarly to the existing "Exists on Other Instance" / "Seeding on Other Instance" cross-instance conditions, but at the filesystem / inode level rather than at the API/metadata level.Technical notes
All reactions