Cannot create config because it already exists, cannot delete because it does not exist.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 160
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 3
Description
When trying to create a config using sudo snapper create-config / an error says there's already a config.
When trying to delete the config using sudo snapper delete-config an error says there's no root config.
ls -la /etc/snapper/configs outputs void because there are no config files there.
sudo snapper list-configs outputs that there are no configs.
Configuration | Sub-volume
--------------+------------
btrfs subvol list / do not present any subvolume with "snapshots" or "@snapshots" name.
Lastly, ls /.snapshots says there no file or directory of that kind.
What kind of voodoo is at work here ? If there's no config to delete, there should be no errors telling me there's already one when creating.
snapper 0.5.4
flags btrfs,lvm,no-ext4,xattrs,rollback,btrfs-quota,no-selinux
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 conflicting results from snapper create-config /, snapper delete-config, and snapper list-configs, then compare them with /etc/snapper/configs, /.snapshots, and btrfs subvol list /. Trace how these commands detect an existing or missing root configuration. Done means the commands consistently report the actual configuration state or clearly explain the discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100