Comment # 7 on bug 997575 from Filipe Manana

(In reply to Oliver Kurz from comment #6)
> Trying to reproduce this on Leap 42.2 Beta1 and also a more recent build:
> In both cases on multiple tries I could somewhat reproduce issues but always
> ending up with an unresponsive system so no helpful logs could be gathered.
> After reboot, when the filesystem tries to replay the journal it takes ages
> and eventually fails with an OOM exception in plymouthd(!) so also there no
> luck.
> 
> I then installed Leap 42.1 and ran the test overnight. It stopped when the
> harddisk capacity was depleted because of snapper snapshots but did not fail
> with any kernel problems so I can assume neither my hardware setup is flawed
> nor that the issue has been in Leap 42.1, of course, testing also on
> btrfs+snapshots.
> 
> Now I will try an upgrade to Leap 42.2 and try again.

Thanks for your attempts to reproduce Oliver.
But I don't think you need to do it. I was able to reproduce it too, even with
an upstream vanilla kernel. It's much easier to reproduce immediately after
installing tumbleweed (on the first boot), but not so easy after building a new
kernel with extra logging/tracing/etc or doing a few balances before.