I recently had a my / run out of space due to snapper snapshots. I then manually deleted a bunch to make space, but I know there is the
command. I tried running it with the cleanup algorithm and got the following output:
Venus:~ # snapper -v cleanup number Deleting snapshot from root: 1 Deleting snapshot failed.
Here is my snapper config for root:
Venus:~ # snapper get-config Key | Value -----------------------+------ ALLOW_GROUPS | ALLOW_USERS | BACKGROUND_COMPARISON | yes EMPTY_PRE_POST_CLEANUP | yes EMPTY_PRE_POST_MIN_AGE | 1800 FSTYPE | btrfs NUMBER_CLEANUP | yes NUMBER_LIMIT | 2-10 NUMBER_LIMIT_IMPORTANT | 4-10 NUMBER_MIN_AGE | 1800 QGROUP | 1/0 SPACE_LIMIT | 0.5 SUBVOLUME | / SYNC_ACL | no TIMELINE_CLEANUP | yes TIMELINE_CREATE | no TIMELINE_LIMIT_DAILY | 10 TIMELINE_LIMIT_HOURLY | 10 TIMELINE_LIMIT_MONTHLY | 10 TIMELINE_LIMIT_WEEKLY | 0 TIMELINE_LIMIT_YEARLY | 10 TIMELINE_MIN_AGE | 1800
Venus:~ # snapper --version snapper 0.5.1 flags btrfs,lvm,no-ext4,xattrs,rollback,btrfs-quota,no-selinux
As far as I understand it, snapshots 0 and 1 can’t be removed and that is why it fails. But why does it try to delete snapshot number 1? Shouldn’t that be excluded from the cleanup? I did use “snapper rollback” before on this installation, maybe that has something to do with it?