You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I understood the logic of janitorr is as followed:
If my free disk space drops below let's say 5 % and the media is older than let's say 3 months, it will be deleted. If the media is older than 3 months minus my setting for leaving soon (let's say 30 days) so 2 months in this example, it will be added to the leaving soon collection instead.
What I'm missing is the following functionality:
If my free space drops below 5 % and the media is older than 3 months, it will be added to the leaving soon collection. If it wasn't watched (or tagged with janitorr_keep) within 30 days it will be deleted. Crucial for me would be that janitorr knows when the media was added to the leaving soon collection (should be easy enough by checking the ctimes of the symlinks, if from-scratch is set to false).
What I'm trying to achieve: If I start using janitorr now after years of running a media server, I want to schedule media for deletion with the possibility to intervene. So even if the media is 2 years old, it should never be deleted right away but only after being X days in the leaving soon collection. Does this make sense to you?
The text was updated successfully, but these errors were encountered:
I'm aware of the leaving soon folder not "going back" if more space opens up or items getting deleted sooner if more space is used. This can't be fixed by observing symlinks creation dates, I'd have to separately store the contents of the leaving-soon directory and that just isn't happening. I don't want to introduce a persistence layer to Janitorr.
It sounds to me, what you're looking for is some kind of recycle bin that gets cleaned up by Janitorr after x days. If you want to submit a PR that doesn't break the current functionality but still makes this possible, please feel free.
Keep in mind, Sonarr and Radarr also have recycle bins you can enable, although I'm not entirely sure how they would interact with Jellyfin's deletion. I imagine at the very least one of two hardlinks should remain.
As things are right now, I don't want to change the operation mode of leaving soon and I don't think this would be in line with Janitorr's mission either. If your media is past its expiration date for a certain disk percentage threshold, it's automatically deleted. This includes the case where a 10% threshold allows an age of 30 days, you drop down to the 5% threshold that specifies 10 days and media that's only 15 days old now instantly gets removed.
The above scenario is exactly what I'm trying to achieve with Janitorr. Automatic cleanup that frees up space so friends and family can request the things they want without the server running out of space.
If you can suggest or create a differently functioning schedule, you could also create one on top of the tag, age and daily schedules. Separating them could allow you to differ vastly from given default functionality. You'd likely not be able to re-use much of the leaving-soon code, but the basics would remain the same.
As far as I understood the logic of janitorr is as followed:
If my free disk space drops below let's say 5 % and the media is older than let's say 3 months, it will be deleted. If the media is older than 3 months minus my setting for leaving soon (let's say 30 days) so 2 months in this example, it will be added to the leaving soon collection instead.
What I'm missing is the following functionality:
If my free space drops below 5 % and the media is older than 3 months, it will be added to the leaving soon collection. If it wasn't watched (or tagged with janitorr_keep) within 30 days it will be deleted. Crucial for me would be that janitorr knows when the media was added to the leaving soon collection (should be easy enough by checking the ctimes of the symlinks, if from-scratch is set to false).
What I'm trying to achieve: If I start using janitorr now after years of running a media server, I want to schedule media for deletion with the possibility to intervene. So even if the media is 2 years old, it should never be deleted right away but only after being X days in the leaving soon collection. Does this make sense to you?
The text was updated successfully, but these errors were encountered: