Question
Timeshift pre-update snapshot abort when the system partition lacks free space in Linux Mint Update Manager
Mira Cedar
0 reputation · 12 Sept 2023, 13:10 UTC
81.5K views
Loading…
0 reputation · 12 Sept 2023, 13:10 UTC
Linux Mint's Update Manager can invoke Timeshift before applying updates, but snapshot creation aborts when the root partition lacks free space or the filesystem is unsupported. On ext4, snapshots rely on rsync and hard links, which consume more time and space than BTRFS subvolume copies and are more likely to hit capacity limits. Timeshift defaults to excluding /home, so a system restore reverts applications and settings but leaves user data untouched; however, changing that exclusion increases snapshot size and may worsen the space pressure that causes the abort.
The unresolved decision is whether to retain the default /home exclusion and accept that user data requires separate backup tooling, or to include /home in snapshots despite larger, slower backups that are more likely to trigger the insufficient-space failure. Retention policy configuration also affects whether automatic snapshots accumulate and eventually fill the partition over time. Behavior varies by Linux Mint version and Timeshift release, so defaults should be verified on the installed system rather than assumed.
Should the default /home exclusion be preserved to minimize snapshot footprint, or does including user data in system snapshots provide a safer rollback path despite the increased risk of pre-update snapshot aborts? What retention thresholds prevent automatic snapshots from exhausting the root partition and reintroducing the failure? What is the correct recovery procedure when an interrupted Timeshift snapshot is retained and blocks subsequent snapshot attempts during Update Manager runs?
33775 reputation · 12 Sept 2023, 16:58 UTC
Preserve the default /home exclusion. It minimizes the snapshot footprint and reduces the chance that Update Manager's pre-update Timeshift call aborts when the root partition is tight on space. Include /home only if you accept slower, larger snapshots and a higher risk of the same insufficient-space failure; user data is better protected by separate backup tooling.
The likely explanation for the abort is that the rsync-based snapshot on ext4 needs free space comparable to changed system files, and accumulated snapshots or an oversized scope gradually consume that headroom. Confirmed facts: Timeshift defaults to excluding /home; on ext4 it uses rsync and hard links, so the first snapshot is large and later ones are incremental; retention counts control how many snapshots accumulate.
Set boot, hourly, daily, weekly, and monthly retention counts to the lowest values that meet your rollback needs. The sum of all retained snapshots must stay well below the free space reported for the root partition. If the root filesystem is small, disable scheduled snapshots entirely and create a manual snapshot only before applying updates. Exact defaults vary by Timeshift version and Linux Mint release, so verify them in the Timeshift GUI or configuration files rather than assuming values.
linuxmint/timeshift/snapshots on the target partition).Run df -h / and compare free space to the size of your latest successful system snapshot. Inspect the Timeshift settings for default exclusions and retention counts. Review Update Manager preferences for the option to create snapshots before updates and its behavior on failure, because the prompt and default differ across Mint releases.
If you have not already confirmed it, what filesystem is your root partition using? On BTRFS, subvolume snapshots are far more space-efficient, so the /home trade-off is different; on ext4 or other rsync-mode filesystems, the guidance above applies directly.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.