Comment # 117 on bug 1063638 from Joachim Banzhaf

Ok, trying to ignor all political and personal stuff and instead add some info:

(repeat: notebook with ssd, 8GB ram, leap 42.3, btrfs root fs, originally it
was leap 42.1, iirc I did not change settings on os level -> suse defaults)

I did not disable quotas yet (and I dont know if they are enabled, I only found
how to disable or enable them, but not how to check their status yet).

I did delete all snapshots with yast (only a few, I did that before)
Then I removed snapper stuff: rpm -e grub2-snapper-plugin-2.02-10.2.noarch
snapper-zypp-plugin-0.5.0-1.1.noarch yast2-snapper-3.2.0-3.5.x86_64
snapper-0.5.0-1.1.x86_64

It did not help. Freezes after starting my notebook today.

I do not find systemd timers related to btrfs, just two cron jobs (probably
because my notebook still runs on leap 42.3). I now disabled the cron jobs.

The cron jobs probably missed some configuration stuff?
cat: /etc/default/btrfsmaintenance: No such file or directory
cat: /etc/system/btrfsmaintenance: No such file or directory
Or is that normal and script defaults are ok?
Where is the output of the script then? I did not find something in the usual
suspects: no /var/log/messages, journalctl | grep btrfs-balance produces an
error (Failed to get journal fields: Bad message) and root mailbox is empty
since december.

I don't know how the timers will work, but I did not like the cron mechanism
that tends to trigger this stuff at startup. It should run only when the system
was idle for some time and only when not on batteries. Only if this strategy
fails for some time, it might be ok to do this at startup and on batteries.
Btw. I also dont like the "windows" way of doing stuff at shutdown. Usually, if
I shut my notebook down I want it to be off fast. If it takes long, I have to
close it, It goes to sleep, and when I need it again, it greats me with
shutdown tasks still going on and a drained battery due to beeing asleep
instead of switched off.

I did not disable quotas yet, because I read the system itself uses them
somehow?
But this will be the next step in a few days regardless.

Finally: Why scrubbing? The idea of scrubbing is to detect failures before you
have multiple of them, because then you cannot repair your raid anymore. Right?
On a notebook I have one SSD with no raid. Also, I do backups on all my
important data, so I have a kind of scrubbing where it matters. So, without
raid it seems like only having heavy drawbacks and no gain?