snapper does not see snapshots created outside @ and @home subvolumes
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 160
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 3
Description
I do not know if it is function of snapper or other software, but on Ubuntu 18 on BTRFS, automatic snapshots pre- and post- apt install snapshots are created in root of the volume, aside from @ and @home directories. Subvolumes start with name @apt... @ is mounted as root, @home is mounted as /home. @apt... subvolumes are not mounted, so snapper does not see it and does not report it
The result it that snapper does not report all btrfs snapshots that are present in filesystem and those invisible snapshots may take disk space. User have to manually delete it.
Is there any configuration that would ensure that pre- and post- apt snapshots are created only by snapper in /.snapshots folder and not in the root of the volume?
Thanks, Jan
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report on Ubuntu 18 with BTRFS, checking snapper alongside the apt pre- and post-install snapshot behavior. Determine whether snapper or other software creates the unmounted @apt... subvolumes, and document the responsible configuration or the missing handling needed so all snapshots are visible and removable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ubuntu
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100