search

openSUSE / snapper

Manage filesystem snapshots and allow undo of system modifications
http://snapper.io/
GNU General Public License v2.0
906 stars 128 forks source link

Cannot create config because it already exists, cannot delete because it does not exist. #421

Open Magissia opened 6 years ago

Magissia commented 6 years ago

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

jhuesos commented 5 years ago

I have the same issue. rookie mistake I delete a config file manually and I can't create a new one with the same name...

sww1235 commented 5 years ago

check under /etc/sysconfig/snapper or your local equivalent. This file contains a list of all configs, so you will probably need to remove the deleted config from there as well.

raldone01 commented 2 years ago

On arch I had to edit /etc/conf.d/snapper. Not particularly user friendly.

blubberdiblub commented 1 year ago

The snapperd background service's idea of what configs exist can get out of date of you create, delete or rename them by hand.

The simple fix for this is to just restart it with systemctl restart snapperd.service. Afterwards its idea should agree again with current reality.