starred/Radarr

Fork 0

mirror of https://github.com/Radarr/Radarr.git synced 2026-03-02 22:57:34 -05:00

Change old movie file torrent label on upgrade #6462

New issue

Open

opened 2026-02-19 23:04:37 -05:00 by deekerman · 11 comments

deekerman commented

2026-02-19 23:04:37 -05:00

Owner

Originally created by @peloyeje on GitHub (Apr 1, 2022).

Is there an existing issue for this?

I have searched the existing issues

When Radarr fetches and downloads a new release as part of a quality upgrade, the trumped movie file is deleted from the root folder but is left as-is in the download client (in my case rtorrent). This behavior is very sensible, but it means that I can find multiple versions for a given movie in my torrent client, without being able to quickly see which one is currently "active" in Radarr.

Describe the solution you'd like

IMHO it would be useful to be able to set a "post-upgrade label" in the Download client config modal (in the same fashion as "post-import"), so trumped movie files are grouped together under a distinct tag.
This would make it possible to add some auto cleaning rules in the torrent client such as:

Seed infinitely for the movies with tag "movies" (active movies)
Seed until 2x ratio (for instance) for the movies with tag "trumped-movies"

Describe alternatives you've considered

Honestly Idk but any idea is welcome :)

Anything else?

N/A

AB#2891

Originally created by @peloyeje on GitHub (Apr 1, 2022). ### Is there an existing issue for this? - [X] I have searched the existing issues ### Is your feature request related to a problem? Please describe When Radarr fetches and downloads a new release as part of a quality upgrade, the trumped movie file is deleted from the root folder but is left as-is in the download client (in my case rtorrent). This behavior is very sensible, but it means that I can find multiple versions for a given movie in my torrent client, without being able to quickly see which one is currently "active" in Radarr. ### Describe the solution you'd like IMHO it would be useful to be able to set a "post-upgrade label" in the Download client config modal (in the same fashion as "post-import"), so trumped movie files are grouped together under a distinct tag. This would make it possible to add some auto cleaning rules in the torrent client such as: - Seed infinitely for the movies with tag "movies" (active movies) - Seed until 2x ratio (for instance) for the movies with tag "trumped-movies" ### Describe alternatives you've considered Honestly Idk but any idea is welcome :) ### Anything else? N/A [AB#2891](https://dev.azure.com/Servarr/7ab38f4e-5a57-4d70-84f4-94dd9bc5d6df/_workitems/edit/2891)

deekerman added the

Type: Feature Request

Area: Download Clients

Status: Unlikely

Status: Needs Triage

labels

2026-02-19 23:04:37 -05:00

deekerman commented

2026-02-19 23:04:38 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Apr 1, 2022):

Basically something similar to what Qbit Manage already does with checking if a file is hardlinked and adjusting accordingly?

Given how versatile rtorrent is, you can probably custom script the same in the client itself.

this seems like a lot of overhead for something that isn't particularly in the scope of *arrs - managing your torrent client and torrents.

@bakerboy448 commented on GitHub (Apr 1, 2022): Basically something similar to what Qbit Manage already does with checking if a file is hardlinked and adjusting accordingly? Given how versatile rtorrent is, you can probably custom script the same in the client itself. this seems like a lot of overhead for something that isn't particularly in the scope of \*arrs - managing your torrent client and torrents.

deekerman commented

2026-02-19 23:04:38 -05:00

Author

Owner

@peloyeje commented on GitHub (Apr 1, 2022):

Basically something similar to what Qbit Manage already does with checking if a file is hardlinked and adjusting accordingly?

Given how versatile rtorrent is, you can probably custom script the same in the client itself.

this seems like a lot of overhead for something that isn't particularly in the scope of *arrs - managing your torrent client and torrents.

Hey,
Didn't know about Qbit manage but yeah exactly like that!
Regarding the custom script alternative, it is definitely doable, but I was hoping the implementation of this feature request could rely heavily on the logic of the "post-import label" to limit overhead: that being said I'm by no means a expert of the codebase, wdyt?

@peloyeje commented on GitHub (Apr 1, 2022): > Basically something similar to what Qbit Manage already does with checking if a file is hardlinked and adjusting accordingly? > > Given how versatile rtorrent is, you can probably custom script the same in the client itself. > > this seems like a lot of overhead for something that isn't particularly in the scope of *arrs - managing your torrent client and torrents. Hey, Didn't know about Qbit manage but yeah exactly like that! Regarding the custom script alternative, it is definitely doable, but I was hoping the implementation of this feature request could rely heavily on the logic of the "post-import label" to limit overhead: that being said I'm by no means a expert of the codebase, wdyt?

deekerman commented

2026-02-19 23:04:38 -05:00

Author

Owner

@codedesperate commented on GitHub (Jul 25, 2022):

I would love to see such a feature!

@codedesperate commented on GitHub (Jul 25, 2022): I would love to see such a feature!

deekerman commented

2026-02-19 23:04:39 -05:00

Author

Owner

@zwimer commented on GitHub (Jan 10, 2024):

Or, related, allow moving the torrent to a different download directory. For example, Radarr might download files to the /downloads/Radarr download directory; but it would be nice if on upgrading a file it might move the old file to /downloads/Radarr-Recycle directory.

@zwimer commented on GitHub (Jan 10, 2024): Or, related, allow moving the torrent to a different download directory. For example, Radarr might download files to the `/downloads/Radarr` download directory; but it would be nice if on upgrading a file it might move the old file to `/downloads/Radarr-Recycle` directory.

deekerman commented

2026-02-19 23:04:39 -05:00

Author

Owner

@zwimer commented on GitHub (Jan 10, 2024):

This would be super appreciated for organizational purposes; it'd make it easy to find 'no longer needed' torrents that we could safely prune when free space is required; without having to monitor each and every download notification to see if we have to manually relocate/relabel some now unnecessary torrent.

@zwimer commented on GitHub (Jan 10, 2024): This would be super appreciated for organizational purposes; it'd make it easy to find 'no longer needed' torrents that we could safely prune when free space is required; without having to monitor each and every download notification to see if we have to manually relocate/relabel some now unnecessary torrent.

deekerman commented

2026-02-19 23:04:39 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Jan 10, 2024):

but it would be nice if on upgrading a file it might move the old file to /downloads/Radarr-Recycle directory.

and

it'd make it easy to find 'no longer needed' torrents that we could safely prune when free space is required

As previously noted - qbitmanage handles this.

@bakerboy448 commented on GitHub (Jan 10, 2024): > but it would be nice if on upgrading a file it might move the old file to /downloads/Radarr-Recycle directory. and > it'd make it easy to find 'no longer needed' torrents that we could safely prune when free space is required As previously noted - qbitmanage handles this.

deekerman commented

2026-02-19 23:04:40 -05:00

Author

Owner

@zwimer commented on GitHub (Jan 10, 2024):

but it would be nice if on upgrading a file it might move the old file to /downloads/Radarr-Recycle directory.

and

it'd make it easy to find 'no longer needed' torrents that we could safely prune when free space is required

As previously noted - qbitmanage handles this.

The hardlinks setting? I'm on a copy-on-write files system so I'm using copies (since COW makes those take negligible space) as that is more flexible as it allows cross-device copies (such as between docker mounts) and work with different linux users, etc.

Or is there some Radarr integration I am unaware of?

@zwimer commented on GitHub (Jan 10, 2024): > > but it would be nice if on upgrading a file it might move the old file to /downloads/Radarr-Recycle directory. > > and > > > it'd make it easy to find 'no longer needed' torrents that we could safely prune when free space is required > > As previously noted - qbitmanage handles this. The hardlinks setting? I'm on a copy-on-write files system so I'm using copies (since COW makes those take negligible space) as that is more flexible as it allows cross-device copies (such as between docker mounts) and work with different linux users, etc. Or is there some Radarr integration I am unaware of?

deekerman commented

2026-02-19 23:04:40 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Jan 10, 2024):

Radarr and qbitmanage have nothing to do with each other.

Please use Discord for support/questions.

@bakerboy448 commented on GitHub (Jan 10, 2024): Radarr and qbitmanage have nothing to do with each other. Please use [Discord](https://radarr.video/discord) for support/questions.

deekerman commented

2026-02-19 23:04:40 -05:00

Author

Owner

@zwimer commented on GitHub (Jan 10, 2024):

I looked into it then further asked on discord as suggested, it would seem that qbitmanage does this via hardlink detection. For people who do hardlink the program should work. Though for people who instead copy (which works well on COW filesystems), it wouldn't be a replacement for the feature being requested above.

@zwimer commented on GitHub (Jan 10, 2024): I looked into it then further asked on discord as suggested, it would seem that qbitmanage does this via hardlink detection. For people who do hardlink the program should work. Though for people who instead copy (which works well on COW filesystems), it wouldn't be a replacement for the feature being requested above.

deekerman commented

2026-02-19 23:04:40 -05:00

Author

Owner

@theelog commented on GitHub (Feb 20, 2024):

This feature would be a life-saver for everyone who's to scared to use Qbitmanage.

@theelog commented on GitHub (Feb 20, 2024): This feature would be a life-saver for everyone who's to scared to use Qbitmanage.

deekerman commented

2026-02-19 23:04:40 -05:00

Author

Owner

@zwimer commented on GitHub (Mar 27, 2024):

Or those who cannot use it / it would be inadequate for. For example, if you have your download client and other client as different users, hardlinks will not work since hardlink users must be the same. Copying works fine, and on a COW filesystem can even be more efficient than hardlinks.

@zwimer commented on GitHub (Mar 27, 2024): Or those who cannot use it / it would be inadequate for. For example, if you have your download client and other client as different users, hardlinks will not work since hardlink users must be the same. Copying works fine, and on a COW filesystem can even be more efficient than hardlinks.