You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2022. It is now read-only.
I have a bind-mount on the root filesystem (/var/www) mounted to a subdirectory (/dev/xxx/www) on the device that is also used as the timeshift target. This causes timeshift to erroneously use that subdirectory for data storage.
Since the source now references the target, the backup will grow in size indefinitely.
Timeshift should have some checks to prevent this.
Recommended behavior
Check if the target is part of the source and warn/stop.
If bind-mounts reference the target device, warn.
If the target backup size starts exceeding the size of the initially calculated source size, warn/stop.
System:
Linux Distribution Name and Version: Linux Mint 19.2
Desktop: Cinnamon
Application Version v19.01 / 19.01.0.2+tina
The text was updated successfully, but these errors were encountered:
Describe the bug
Timeshift filled up my 1.2 TB SSD completely.
I have a
bind-mount
on the root filesystem (/var/www
) mounted to a subdirectory (/dev/xxx/www
) on the device that is also used as the timeshift target. This causes timeshift to erroneously use that subdirectory for data storage.Since the source now references the target, the backup will grow in size indefinitely.
Timeshift should have some checks to prevent this.
Recommended behavior
System:
The text was updated successfully, but these errors were encountered: