Snapper snapshots preserve recovery points but can retain unwanted data. Deleting selected snapshots or reviewed batches in openSUSE and SLES leaves the active filesystem and required boot snapshots in place.

Snapper stores snapshots inside named configurations such as root and tracks each snapshot by numeric ID, type, cleanup policy, and description. Deletion affects only the selected configuration, so snapshots of other subvolumes have separate lists and need separate decisions about what to keep.

Deleting a snapshot permanently removes that restore point. Btrfs shares data blocks between the live filesystem and snapshots, so deleting snapshot IDs does not guarantee a particular amount of reclaimed space. Blocks still referenced by live files or retained snapshots remain in use.

Step-by-step video guide:

Steps to delete Snapper snapshots in openSUSE and SLES:

  1. List available Snapper configurations to identify the subvolume that needs cleanup.
    $ sudo snapper list-configs
    Config | Subvolume
    -------+----------
    root   | /

    The default configuration is named root. The examples use root for the root filesystem; another configuration needs its own name and subvolume path.

  2. List snapshots in the chosen configuration.
    $ sudo snapper -c root list
      # | Type   | Pre # | Date                     | User | Cleanup | Description            | Userdata
    ----+--------+-------+--------------------------+------+---------+------------------------+---------
     0  | single |       |                          | root |         | current                |
     1* | single |       | Fri Nov  6 15:25:36 2026 | root |         | active root filesystem |
     2  | single |       | Fri Nov  6 15:26:03 2026 | root | number  | old recovery point     |
     3  | pre    |       | Fri Nov  6 15:26:03 2026 | root | number  | before package change  |
     4  | post   |     3 | Fri Nov  6 15:26:03 2026 | root | number  | after package change   |
     5  | pre    |       | Fri Nov  6 15:26:03 2026 | root | number  | before package change  |
     6  | post   |     5 | Fri Nov  6 15:26:03 2026 | root | number  | after package change   |
     7  | pre    |       | Fri Nov  6 15:26:03 2026 | root | number  | before package change  |
     8  | post   |     7 | Fri Nov  6 15:26:03 2026 | root | number  | after package change   |
     9  | pre    |       | Fri Nov  6 15:26:03 2026 | root | number  | before package change  |
    10  | post   |     9 | Fri Nov  6 15:26:03 2026 | root | number  | after package change   |

    On Btrfs, - marks the active snapshot, + marks the default for the next boot, and * marks both.

    “Delete all snapshots” can only mean every removable recovery point in this configuration, not every row in the list. Snapshot 0 and the active or default Btrfs snapshots cannot be deleted. Snapper does not protect anything else, so leave out any recovery point you still need, and remove a pre snapshot together with its matching post snapshot.

  3. Delete a single snapshot by number.
    $ sudo snapper -c root delete 2

    This permanently removes snapshot 2 as a recovery point. The IDs shown here belong to the displayed list, not necessarily your system.

  4. Delete a range of unwanted snapshots.
    $ sudo snapper -c root delete 3-10

    The range includes both endpoints. Here, deleting 2 and 3-10 removes all removable snapshots while retaining 0 and 1*. If a recovery point you need lies inside a range, split the range around it.

    With --sync after delete, the command waits until Btrfs has finished releasing the space.

  5. List snapshots again to confirm the deleted IDs are gone.
    $ sudo snapper -c root list
     # | Type   | Pre # | Date                     | User | Cleanup | Description            | Userdata
    ---+--------+-------+--------------------------+------+---------+------------------------+---------
    0  | single |       |                          | root |         | current                |
    1* | single |       | Fri Nov  6 15:25:36 2026 | root |         | active root filesystem |

    IDs 2-10 are gone, while 0 and the active/default snapshot 1* remain.

Share this guide