http://bugzilla.suse.com/show_bug.cgi?id=937047 http://bugzilla.suse.com/show_bug.cgi?id=937047#c1 --- Comment #1 from Achim Gratz --- On closer inspection that snapshot won't be automatically cleaned up, which is a relief: # snapper list Type | # | Pre # | Date | User | Cleanup | Description | Userdata -------+------+-------+--------------------------+------+----------+-------------------+-------------- single | 0 | | | root | | current | single | 1 | | Fri Nov 21 20:30:01 2014 | root | timeline | timeline | single | 145 | | Mon Dec 1 07:45:01 2014 | root | timeline | timeline | single | 353 | | Fri Jan 2 20:15:01 2015 | root | timeline | timeline | single | 1902 | | Thu Jun 4 06:45:01 2015 | root | timeline | timeline | single | 1974 | | Mon Jun 8 23:58:50 2015 | root | | | pre | 1977 | | Tue Jun 9 06:58:56 2015 | root | number | zypp(zypper) | important=yes post | 1978 | 1977 | Tue Jun 9 07:01:42 2015 | root | number | | important=yes pre | 1979 | | Tue Jun 9 07:07:53 2015 | root | number | zypp(packagekitd) | important=no post | 1980 | 1979 | Tue Jun 9 07:08:29 2015 | root | number | | important=no pre | 1986 | | Wed Jun 10 20:08:39 2015 | root | number | zypp(packagekitd) | important=no post | 1987 | 1986 | Wed Jun 10 20:11:03 2015 | root | number | | important=no pre | 1992 | | Thu Jun 11 06:33:30 2015 | root | number | zypp(zypper) | important=no post | 1993 | 1992 | Thu Jun 11 06:33:32 2015 | root | number | | important=no pre | 1999 | | Fri Jun 12 07:11:15 2015 | root | number | zypp(packagekitd) | important=no post | 2000 | 1999 | Fri Jun 12 07:12:35 2015 | root | number | | important=no pre | 2004 | | Fri Jun 12 19:54:19 2015 | root | number | zypp(packagekitd) | important=no post | 2005 | 2004 | Fri Jun 12 19:55:10 2015 | root | number | | important=no pre | 2006 | | Fri Jun 12 19:55:32 2015 | root | number | zypp(packagekitd) | important=no post | 2007 | 2006 | Fri Jun 12 19:55:56 2015 | root | number | | important=no pre | 2012 | | Sat Jun 13 08:14:58 2015 | root | number | zypp(packagekitd) | important=no post | 2013 | 2012 | Sat Jun 13 08:15:02 2015 | root | number | | important=no pre | 2020 | | Sat Jun 20 12:09:15 2015 | root | number | zypp(packagekitd) | important=yes pre | 2021 | | Sat Jun 20 12:09:41 2015 | root | number | zypp(packagekitd) | important=yes post | 2022 | 2021 | Sat Jun 20 12:13:10 2015 | root | number | | important=yes pre | 2043 | | Sun Jun 21 20:35:00 2015 | root | number | zypp(zypper) | important=no post | 2044 | 2043 | Sun Jun 21 20:35:03 2015 | root | number | | important=no pre | 2046 | | Sun Jun 21 21:45:41 2015 | root | number | zypp(packagekitd) | important=no post | 2047 | 2046 | Sun Jun 21 21:45:56 2015 | root | number | | important=no pre | 2048 | | Mon Jun 22 08:05:34 2015 | root | number | zypp(packagekitd) | important=no post | 2049 | 2048 | Mon Jun 22 08:05:49 2015 | root | number | | important=no pre | 2069 | | Tue Jun 23 19:57:27 2015 | root | number | zypp(packagekitd) | important=no post | 2070 | 2069 | Tue Jun 23 19:57:30 2015 | root | number | | important=no single | 2074 | | Wed Jun 24 07:30:01 2015 | root | timeline | timeline | pre | 2078 | | Thu Jun 25 07:09:54 2015 | root | number | zypp(packagekitd) | important=no post | 2079 | 2078 | Thu Jun 25 07:10:54 2015 | root | number | | important=no single | 2080 | | Thu Jun 25 07:15:01 2015 | root | timeline | timeline | single | 2087 | | Fri Jun 26 07:45:01 2015 | root | timeline | timeline | single | 2091 | | Sat Jun 27 09:30:01 2015 | root | timeline | timeline | pre | 2093 | | Sat Jun 27 10:34:50 2015 | root | number | zypp(packagekitd) | important=no post | 2094 | 2093 | Sat Jun 27 10:35:58 2015 | root | number | | important=no single | 2104 | | Sun Jun 28 07:15:01 2015 | root | timeline | timeline | pre | 2112 | | Sun Jun 28 14:31:42 2015 | root | number | zypp(packagekitd) | important=no post | 2113 | 2112 | Sun Jun 28 14:31:54 2015 | root | number | | important=no single | 2121 | | Mon Jun 29 08:00:01 2015 | root | timeline | timeline | single | 2122 | | Tue Jun 30 07:00:01 2015 | root | timeline | timeline | pre | 2128 | | Wed Jul 1 06:24:49 2015 | root | number | zypp(packagekitd) | important=no post | 2129 | 2128 | Wed Jul 1 06:25:56 2015 | root | number | | important=no single | 2130 | | Wed Jul 1 06:30:01 2015 | root | timeline | timeline | single | 2135 | | Wed Jul 1 23:00:01 2015 | root | timeline | timeline | single | 2136 | | Thu Jul 2 06:45:01 2015 | root | timeline | timeline | single | 2137 | | Thu Jul 2 22:15:01 2015 | root | timeline | timeline | single | 2138 | | Thu Jul 2 23:15:01 2015 | root | timeline | timeline | single | 2139 | | Fri Jul 3 07:15:01 2015 | root | timeline | timeline | single | 2140 | | Fri Jul 3 17:45:01 2015 | root | timeline | timeline | single | 2141 | | Fri Jul 3 18:45:01 2015 | root | timeline | timeline | pre | 2142 | | Fri Jul 3 19:27:17 2015 | root | number | yast snapper | single | 2143 | | Fri Jul 3 19:45:01 2015 | root | timeline | timeline | post | 2144 | 2142 | Fri Jul 3 19:47:24 2015 | root | number | | single | 2145 | | Fri Jul 3 20:45:01 2015 | root | timeline | timeline | single | 2146 | | Fri Jul 3 21:45:01 2015 | root | timeline | timeline | That still leaves the question why it is possible to include such a snapshot in a delete request and why the attempt to delete it brings the system in such a sorry state. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937047 http://bugzilla.suse.com/show_bug.cgi?id=937047#c2 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com Assignee|bnc-team-screening@forge.pr |aschnell@suse.com |ovo.novell.com | --- Comment #2 from Arvin Schnell --- When the system is installed with YaST snapper does add .snapshots to fstab. Why the system gets unstable when trying to delete the default snapshot is not clear to me since the kernel ioctl to delete the snapshot simply fails. I will have a closer look when time permits but more information is welcome. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937047 http://bugzilla.suse.com/show_bug.cgi?id=937047#c4 --- Comment #4 from Thorsten Kukuk --- (In reply to Achim Gratz from comment #0)

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.

This sounds like your system wasn't setup for rollback. Else /.snapshots should have been added to /etc/fstab already. Could it be that this was an upgrade from something older/short before rollback was fully introduced in openSUSE?

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

When you called snapper rollback, snapper told you that this snapshot is the new default root filesystem. What else do you expect?

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.

snapper cleanup algorighm will not delete the subvolume with the current root filesystem. So this is can really only happen if you try to manual delete that snapshot. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937047 http://bugzilla.suse.com/show_bug.cgi?id=937047#c6 --- Comment #6 from Achim Gratz --- (In reply to Arvin Schnell from comment #2)

When the system is installed with YaST snapper does add .snapshots to fstab.

The system was a fresh install from openSUSE-Tumbleweed-DVD-x86_64-Snapshot20141112-Media.iso copied to a USB stick. The default settings for a btrfs / were accepted.

Why the system gets unstable when trying to delete the default snapshot is not clear to me since the kernel ioctl to delete the snapshot simply fails. I will have a closer look when time permits but more information is welcome.

Yes, thankfully the subvolume itself was _not_ deleted. But somehow all filesystems had been unmounted anyway before that was attempted. The system didn't really crash, but with neither /proc nor /dev available you can't do anything useful anymore, not even shut down. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937047 http://bugzilla.suse.com/show_bug.cgi?id=937047#c7 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Stromeko@NexGo.DE Flags| |needinfo?(Stromeko@NexGo.DE | |) --- Comment #7 from Arvin Schnell --- (In reply to Achim Gratz from comment #6)

(In reply to Arvin Schnell from comment #2)

The system was a fresh install from openSUSE-Tumbleweed-DVD-x86_64-Snapshot20141112-Media.iso copied to a USB stick. The default settings for a btrfs / were accepted.

That exact version seems to be impossible to find half a year later.

...

Why the system gets unstable when trying to delete the default snapshot is not clear to me since the kernel ioctl to delete the snapshot simply fails. I will have a closer look when time permits but more information is welcome.

Yes, thankfully the subvolume itself was _not_ deleted. But somehow all filesystems had been unmounted anyway before that was attempted. The system didn't really crash, but with neither /proc nor /dev available you can't do anything useful anymore, not even shut down.

I tried that myself with openSUSE 13.2 and the 'snapper delete' command does the ioctl to delete the btrfs subvolume which fails and that is it. Snapper does no umount in that situation (and never a umount of /dev or /proc). So I need more information about the "somehow" or exact steps how the reproduce the issue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937047 http://bugzilla.suse.com/show_bug.cgi?id=937047#c9 --- Comment #9 from Achim Gratz --- (In reply to Arvin Schnell from comment #7)

That exact version seems to be impossible to find half a year later.

In any case, it's a Tumbleweed install from that date, updated ever since. It should be possible to find out which way the system and snapper was installed by that version and what (if any) changes the updates should have introduced.

I tried that myself with openSUSE 13.2 and the 'snapper delete' command does the ioctl to delete the btrfs subvolume which fails and that is it. Snapper does no umount in that situation (and never a umount of /dev or /proc).

openSUSE 13.2 != Tumbleweed, I'd think.

So I need more information about the "somehow" or exact steps how the reproduce the issue.

1. Boot into a snapshot, rollback. 2. Keep on working from the rollback snapshot, including more snapshots being created. 3. Try to 'snapper rm #-of-rollback. That's it. Since you're left with only the bash builtins at that point there's not a whole lot more I can tell you, sorry. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937047 http://bugzilla.suse.com/show_bug.cgi?id=937047#c11 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Stromeko@NexGo.DE | |) | --- Comment #11 from Arvin Schnell --- With openSUSE-Tumbleweed-DVD-x86_64-Snapshot20150705-Media.iso I can reproduce the issue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937047 http://bugzilla.suse.com/show_bug.cgi?id=937047#c13 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel --- Comment #13 from Arvin Schnell --- Looks like a kernel issue. Note that on openSUSE 13.2 the error message from btrfs is "Device or resource busy" while on Tumbleweed 20150705 it is "Operation not permitted". -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937047 http://bugzilla.suse.com/show_bug.cgi?id=937047#c14 David Sterba changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dsterba@suse.com --- Comment #14 from David Sterba --- You can't delete the s(In reply to Achim Gratz from comment #9)

1. Boot into a snapshot, rollback. 2. Keep on working from the rollback snapshot, including more snapshots being created. 3. Try to 'snapper rm #-of-rollback.

You can't remove the snapshot that's currently mounted (EBUSY) or set as the default subvolume (EPERM). See if system log contains something like "deleting default subvolume <number> is not allowed". -- You are receiving this mail because: You are on the CC list for the bug.