search

linuxmint / timeshift

System restore tool for Linux. Creates filesystem snapshots using rsync+hardlinks, or BTRFS snapshots. Supports scheduled snapshots, multiple backup levels, and exclude filters. Snapshots can be restored while system is running or from Live CD/USB.
2.39k stars 86 forks source link

Unable to Terminate or Interact with Scheduled Backup Process When Disk Is Full #240

Open PeterDaveHello opened 11 months ago

PeterDaveHello commented 11 months ago

Describe the bug

During a scheduled backup, the disk (partition) became full, triggering a system notification about the lack of storage space. I attempted to open the Timeshift GUI to see if old snapshots could be deleted. However, a dialog with a title ? appeared in the Taskbar/Panel, stating "Scheduled snapshot in progress..." and "Another instance of Timeshift is creating a snapshot. Please wait a few minutes and try again," as shown below:

image

image

Upon double-checking the system tray, I noticed that the snapshot creation was still ongoing, as indicated by the message "A Timeshift system snapshot is being created":

image

Double-clicking or right-clicking the icon produced no response, menu, or options, and there were no interactive windows available. This situation has persisted for approximately five hours without any changes, meaning the application did not terminate or resolve the issue on its own. As a result, there was no proper way to terminate or interact with the ongoing process except by directly killing it.

To Reproduce

I have not had the opportunity to reproduce this issue yet, as the problem is still ongoing. Reporting it here for now.

Expected behavior

  1. The application should detect a disk-full condition and terminate the backup process accordingly.
  2. The system tray icon should allow for menu or window pop-up interactions to pause or end the process.

System:

PeterDaveHello commented 11 months ago

I used sudo killall timeshift to terminate the hanging process. The system tray icon disappeared as a result. This allowed me to launch a new Timeshift instance successfully, and I was able to clean up old backups.

PeterDaveHello commented 11 months ago

Upon further inspection, a residual backup was discovered in /timeshift/snapshots. This is suspected to be a remnant of the backup process that was manually killed. The backup was not displayed in the Timeshift interface and had to be manually removed.