Feature Request: Add option to instead of specifying how many snapshots to keep, how much space snapshots are allowed to use
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- linux
- Domain
- desktop
Research direction
Start by reading the Schedule menu in the Timeshift settings window and tracing how snapshot retention is configured and how current snapshot disk usage could be measured. The request leaves design choices open, including percentage versus gigabytes and how a space limit combines with a minimum snapshot count. Done means users can configure a space limit and Timeshift respects it when deciding how many snapshots to keep.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
I had the value for how many snapshots to keep set rather high (~30) in timeshift and then had it fill up 100GB of disk space,
since I did not know how much space they were going to use. (Though I could have guessed)
At one point I had unknowingly filled up my 160GB Linux partition with mostly timeshift snapshots.
Describe the solution you'd like
In the "Schedule" Menu in the timeshift settings window I would like an extra option that allows you to specify the maximum amount of disk space for timeshift to use.
There should be options for both how many percent of the disk space you want to allow timeshift to use,
as well as how many gigabytes, so users can chose one or the other, depending how they want to configure it.
In a similar fashion like how you specify how much size that System Restore Points are allowed to use on Windows.
So that way instead of only being able to specify the maximum amount of snapshots you allow timeshift to keep, you can specify how much disk space it is allowed to occupy,
as right now when configuring the amount of backups to keep you are always guessing the disk space usage.
This would require timeshift to measure how much disk space it is using to gauge how many snapshots it can
keep.
It would be even better if there was the possibility to combine snapshot amount and max diskspace usage so you can for example set it up to always keep at least 5 snapshots and possibly more if they use less than 10% of disk space.
- Dominant language
- Vala
- Stars
- 4.3k
- Forks
- 158
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/timeshift
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
All issues in linuxmint/timeshift
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
NousResearch/hermes-agent#134960 ·
Maintainers usually reply within 1 day
-
app enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Y-ASLant/ElegantClipboard#166 ·
-
Lid close does not lock the session on Apple Silicon (lid-close bind skips omarchy-system-lid-close)Open
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
omacom/omarchy-mac#701 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day