Diagnosing and Fixing Timeshift Snapshot Failures on Linux Mint

Recognizable Condition

Users report that Timeshift either refuses to create a new snapshot or consumes all available disk space quickly. The system may become unresponsive, or a recent rollback restores a state that is too old. These symptoms indicate a problem with snapshot creation, retention policy, or disk usage.

Cause & Diagnostic Table

Cause	Symptom	Quick Check	Immediate Fix
Insufficient free space on the destination partition	Timeshift aborts with "No space left on device"	Run df -h /var/lib/timeshift	Delete old snapshots or increase the destination size
Retention policy set too aggressively	Snapshots keep piling up beyond the configured limit	Check /etc/timeshift/timeshift.json for "snapshot_count"	Reduce snapshot_count or enable automatic purge
Timeshift running as a non‑root user	Snapshot creation fails with permission errors	Verify user privileges via whoami	Run Timeshift as root or add sudo to the command
Root filesystem not supported for incremental snapshots	Timeshift logs “Unsupported filesystem”	Check lsblk -f for BTRFS or EXT4	Switch to a supported filesystem or use the rsync mode
Corrupted Timeshift database	Timeshift lists no snapshots or crashes	Inspect /var/log/timeshift.log	Re‑initialize Timeshift via sudo timeshift --delete-all and recreate snapshots

Ordered Checks

1. Verify Disk Space – The snapshot destination is usually /var/lib/timeshift. Run:

   df -h /var/lib/timeshift
   

   Check that the available space exceeds the size of the largest snapshot you plan to keep.

2. Inspect Retention Settings – Open the JSON config:

   sudo nano /etc/timeshift/timeshift.json
   

   Look for "snapshot_count": 10 and "max_size": "10GB". Adjust these values if you notice excessive accumulation.

3. Confirm User Privileges – Timeshift must run as root to access system files. Check with:

   whoami
   

   If you are not root, prefix commands with sudo or run the GUI as an administrator.

4. Check Filesystem Compatibility – Use:

   lsblk -f
   

   If the root partition shows EXT4 or BTRFS, Timeshift can create snapshots. For other filesystems, Timeshift falls back to rsync and will copy the entire tree, consuming more space.

5. Review Timeshift Logs – Errors are recorded in /var/log/timeshift.log. Search for recent entries:

   grep -i "error" /var/log/timeshift.log | tail -n 20
   

6. List Existing Snapshots – Ensure the snapshot list is populated:

   timeshift --list
   

   If no snapshots appear, the database may be corrupted.

Fixes Tied to Findings

• Freeing Space – Delete the oldest snapshot manually:

  sudo timeshift --delete 2023-08-01-12-00-00
  

  or purge all old snapshots:

  sudo timeshift --delete-all
  

• Adjusting Retention Policy – Edit the JSON file to keep only the last five snapshots and cap total size at 8 GB:

  {
      "snapshot_count": 5,
      "max_size": "8GB"
  }
  

• Running as Root – Launch the GUI from a terminal with sudo timeshift-gtk or use the command line:

  sudo timeshift --create
  

• Switching Filesystem Mode – If you’re on a non‑supported filesystem, re‑configure Timeshift to use rsync:

  sudo timeshift --set-fs-type rsync
  

• Re‑initializing the Database – When logs show corruption:

  sudo timeshift --delete-all
  sudo timeshift --create
  

Concrete Example: Setting a 5‑Snapshot Retention with 10 GB Limit

Assume you have a 20 GB SSD and want to prevent Timeshift from filling it. Open the configuration file:

sudo nano /etc/timeshift/timeshift.json

Modify the relevant keys:

{
    "snapshot_count": 5,
    "max_size": "10GB",
    "interval": {
        "hourly": true,
        "daily": false
    }
}

Save and exit. Verify the new settings with:

timeshift --list

When the next snapshot is created, Timeshift will automatically delete the oldest snapshot if the total size exceeds 10 GB.

Escalation Criteria

1. If after adjusting retention and freeing space Timeshift still cannot create a snapshot, check the logs for permission or mount errors. If the root partition is mounted read‑only (common after a crash), remount it read‑write with sudo mount -o remount,rw / before retrying.

2. When the log shows Cannot open /dev/disk/by-uuid/…: Permission denied, the issue is likely a missing sudo or a mis‑configured sudoers file. Ensure the user is part of the sudo group.

3. If Timeshift continues to crash with segmentation faults, confirm that the package is up to date:

   sudo apt update && sudo apt install --reinstall timeshift
   

   If the problem persists, consider filing a bug report with the Linux Mint developers, attaching /var/log/timeshift.log and the output of timeshift --list.

Practical Verification

After applying a fix, create a test snapshot and then roll it back to confirm the system returns to the expected state:

sudo timeshift --create
sudo timeshift --restore 2024-01-01-12-00-00

Check that user data on separate partitions (e.g., /home) remains untouched and that system binaries are restored to the snapshot version.

Limitations

• Timeshift only snapshots the root filesystem; user data on other partitions is not affected by rollback.
• Incremental snapshots rely on free space for delta storage; rapid snapshot creation on a small SSD can still exhaust space quickly.
• Rolling back to a snapshot older than a few weeks may miss recent security updates, potentially exposing the system to vulnerabilities.