pbear wrote: ↑
Sat May 02, 2020 8:54 pm
Pjotr wrote: ↑
Sat May 02, 2020 3:00 pm
Not FUD, but fact. I recall several reports on this forum from people who got into trouble by Timeshift disk usage getting out of hand. Too lazy to dig 'em up for you, but they were there. In these cases I suspect the ballooning effect of frequently updated Flatpaks.
So I do the obvious thing and run a Forum search, planning to look at the last six months. Nothing, except a chat thread
where you made the same claim. (No one in the thread reports the problem.) Okay, now I have to keep going. Another six months back, still nothing. At this point, I'm on page 5 of 8, so might as well finish. Two pages later, I'm getting desperate. There can't really be no one
. Can't find 'em though. Try the common misspelling, Flatpack with a "c". Another page of results, but no hits. No doubt, I could have missed one, even two, but this isn't actually a problem. It's FUD.
Improve your search-fu. It's in dire need of an upgrade. You should search for Timeshift disk usage getting out of hand, irrespective whether the causes were clear (besides the sheer number of stored snapshots). No more than four weeks ago:
The initial problem was caused by the partition being full at the time of the updates (due to having too many TimeShift snapshots on it; since corrected), and this is what caused the failure to log in
No mention of Flatpaks, I grant you that, but the most probable reason why
Timeshift snapshots might start ballooning in the first place
, is frequently updating Flatpaks. Not many other common causes come to mind.
Sometimes people aren't even aware that they've installed some applications as Flatpaks. Let alone what the consequences might be for the size of their Timeshift snapshots. So they won't mention it in their help request if they did.
And for forum helpers it's not worthwhile to ask any further in such cases: the simple practical recommendation to reduce the bloody number of snapshots usually suffices to solve their issues. If it does: problem solved. Next please.
I'm too lazy to dig up more examples for you, but I recall that there were more instances of ballooning Timeshift snapshots in the not too distant past. If you want to spend time and energy on finding them, if only to work on your search skills: happy digging.
In any case: the main issue here is, that in general it definitely *is* advisable to severely limit the number of stored Timeshift snapshots
. As a practical rule of thumb.
that two stored snapshots (if automated: with a monthly interval) are sufficient for nearly everyone and will almost certainly prevent Timeshift disk usage ever getting out of hand. Even with Flatpaks galore. Quod erat demonstrandum.