Repository navigation
[FR] Hardlink counter #957
Replies: 2 comments 1 reply
|
If you're using hardlinked data, then deletion should not matter, since that's basically the point of hardlinking. I like the idea of cross seed management though, hence the pr. |
Agent BriefCategory: enhancement Current behavior:
The torrent table itself has no hardlink column, no hardlink filter, and no context-menu entry that lists the torrents sharing the data of a torrent. Outside the delete dialog, that answer still needs a manual filesystem check. Desired behavior:
Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Feature scope is a maintainer call. Two decisions sit inside it: what the column shows (a raw link count, which is honest but hard to act on, against the scope classification the automation engine already produces), and whether the torrent list may carry filesystem-derived data at all, since that data costs a file-identity scan across the instance and the table is the hottest path in the app. |
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
Recently, a column was added to indicate unregistered or otherwise dead torrents. This is useful when managing single items, but when using something like cross-seed, it becomes a little more complicated.
Before deleting an item, you need to know if other torrents are using that same data. Without this manual check, you either end up deleting still-seeded data, or end up with orphaned data on your array.
Describe the solution you'd like
Two possible solutions in mind, one easier and one harder, but each with their own benefits. Each require a fs mount.
The first method is probably more likely, as the second is much more involved.
It would be additionally beneficial to be able to right click and view all other items using that hardlinked data, but that's a bit more involved and niche.
Describe alternatives you've considered
Manual searching, and management containers.
All reactions