Comment # 97 on bug 1063638 from Thomas Rother

(In reply to Harald Achitz from comment #95)
> this bug has a history back to 2016 and has been declared resolved
> I requested if there have been meaningful tests been done, you can look up
> the answer.
> https://bugzilla.opensuse.org/show_bug.cgi?id=1017461#c110
> 
> It seems either the responsible person do not understand the problem, or
> they want to hide something. I guess both is the case.
> But obviously they either don't care, or do not know how to reproduce this
> behavior do do meaningful development for this problem. I guess both is the
> case.
> 
> With the history of this bug and the stubborn ignorance in handling this
> problem, while providing no meaningful documentation/wiki for this problem
> at all I have to say: To bad to see that SuSE is not something I can
> recommend anymore to anyone

I would strongly support Olivers statement, but I also understand your own
frustation. I also had this issue on two laptops back in the OpenSUSE 42.3
times. In the office we also have SLES machines with btrfs but without ANY
similar issues. I followed some of the published workarounds and since Leap 15
I haven't seen the issue for a long time on both laptop machines.  But I don't
really know why it disappeared finally.

Some issues even in the open source field take a long time to solve and the
best way to help is to describe the setups and situations where it appears in
detail to make it reproducible for others.