Looks like you forgot to unmount /mnt/timeshift/backup after app close in btrfs mode.
Djaler
All 7 comments
It's intentional. There's no harm in leaving it mounted for the next scheduled backup.
teejee2008
on 10 Sep 2017
It works wrong with btrfs. Nested snapshots created
Djaler
on 10 Sep 2017
umount snapshot is an important feature, for example it saves you if you accidentally type a command that damages the system: "sudo rm -rf / *".
I made a video on this feature that had timeshift-btrfs, ie the ability to restore the system after typing the command that damages the whole system (sudo rm -rf / *): https://www.youtube.com/watch?v=VdmDJ3cBmZM&t=250s
With timeshift I tried, it also eliminates the snapshot, so it is no longer possible to recover the system.
emanuc
on 27 Feb 2018
Can we reopen this as feature request? I too think that leaving mounted snapshots is bad idea.
Stibila
on 22 Jul 2018
IMHO, this can be related to #141
Djaler
on 22 Jul 2018
Could you put a flag if setting a snapshot in RO?
So another advantage is that you could use "btrfs send" to export it to another disk.
btrfs property set -ts /path/to/snapshot ro true
https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-property#btrfs-property.288.29_manual_page
emanuc
on 11 Apr 2020
I also would like to have this in rsync mode.
I guess, this woul枚d also solve this unexpected behaviour:
https://github.com/teejee2008/timeshift/issues/675
Golddouble
on 7 Dec 2020
Related issues
Dude4Linux
路
6Comments
ghost
路
9Comments
giswqs
路
5Comments
dm2912
路
8Comments
q2dg
路
15Comments
Most helpful comment
Could you put a flag if setting a snapshot in RO?
So another advantage is that you could use "btrfs send" to export it to another disk.
btrfs property set -ts /path/to/snapshot ro truehttps://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-property#btrfs-property.288.29_manual_page