Timeline for How to delete btrfs subvolumes with <FS_TREE> in their name
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 25, 2019 at 19:15 | history | edited | mchid | CC BY-SA 4.0 |
clarification
|
| Oct 25, 2019 at 18:45 | comment | added | user44400 |
Note that apt-btrfs-snapshot is not "built in" in every distribution. In particular it seem not to be available in the Debian repositories.
|
|
| Jul 28, 2016 at 9:40 | history | edited | mchid | CC BY-SA 3.0 |
added 157 characters in body
|
| Nov 30, 2015 at 23:10 | history | edited | mchid | CC BY-SA 3.0 |
added 880 characters in body
|
| Nov 29, 2015 at 7:45 | history | edited | mchid | CC BY-SA 3.0 |
added 4 characters in body
|
| Nov 29, 2015 at 7:14 | comment | added | mchid | @Cactus although, oldroot should not delete and can still be used as a restore point. | |
| Nov 29, 2015 at 7:13 | comment | added | mchid |
@Cactus if all your snapshots are older than 30 days then, that's what should happen. To verify this before you start, you can run: sudo apt-btrfs-snapshot list-older-than 30d to see what is older than 30 days.
|
|
| Nov 29, 2015 at 6:42 | comment | added | Cactus |
I've just tried this, and sudo apt-btrfs-snapshot delete-older-than 30d proceeded to delete ALL snapshots...
|
|
| Nov 14, 2015 at 1:42 | history | answered | mchid | CC BY-SA 3.0 |