Bug ID 937047
Summary snapper rollback changes default subvolume
Classification openSUSE
Product openSUSE Factory
Version 201505*
Hardware x86-64
OS openSUSE 13.2
Status NEW
Severity Major
Priority P5 - None
Component Basesystem
Assignee bnc-team-screening@forge.provo.novell.com
Reporter Stromeko@NexGo.DE
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

After a snapper boot rollback, the default btrfs subvolume has changed to the
snapshot I've rolled back to.  This had several undesirable consequences:

1. Snapper stopped working since /.snapshots wasn't populated any more.  I've
fixed that by adding the .snapshots subvolume to /etc/fstab.

2. One of the snapshots listed by snapper is actually the new default
subvolume, but that's not marked in any way.

3. Trying to delete that snapshot leaves the system in an unusable state with
most filesystems unmounted.  You can only switch off hard at that point.  The
snapper cleanup hasn't gotten to that snapshot yet, but when it does it might
produce the same crash then.


You are receiving this mail because: