Hi,
I have the following snapshot scheme:
$ snapper list
Type | # | Pre # | Date | User | Cleanup |
Description | Userdata
-------+-----+-------+--------------------------+------+---------+-----------------------+-------------
single | 0 | | | root | |
current |
single | 1 | | Thu Apr 16 22:07:21 2015 | root | |
first root filesystem |
single | 329 | | Sat May 23 16:24:19 2015 | root | |
|
pre | 377 | | Fri Jun 12 16:57:39 2015 | root | number |
zypp(zypper) | important=no
post | 378 | 377 | Fri Jun 12 16:57:40 2015 | root | number |
| important=no
pre | 379 | | Sat Jun 13 21:35:43 2015 | root | number |
yast snapper |
or
$ btrfs subvolume list /
ID 257 gen 67733 top level 5 path .snapshots
ID 258 gen 67694 top level 257 path .snapshots/1/snapshot
...
ID 276 gen 66670 top level 258 path .snapshots/1/snapshot/var/lib/machines
ID 642 gen 67730 top level 257 path .snapshots/329/snapshot
ID 694 gen 67694 top level 257 path .snapshots/377/snapshot
ID 695 gen 67694 top level 257 path .snapshots/378/snapshot
ID 697 gen 67729 top level 257 path .snapshots/379/snapshot
When I try to remove the snapshot 329, I get custom errors everytime:
* system freezes completely (the most frequent outcome)
* systems becomes absolutely unresponsive, i.e. can't run processes,
can't connect to dbus, etc.
* some error message comes out.
This snapshot appeared on its own when I was cleaning other pre-post
snapshots in "snapper".
The OS is OpenSUSE: kernel 4.0.5, btrfs-progs v4.0+20150429
Is it an expected behaviour?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
