Comment # 60 on bug 1063638 from Ronan Chagas

(In reply to Richard Brown from comment #53)
> While the load condition is reproducible, and I can confirm that pressing
> the reset-switch during a high-load btrfs condition MAY make the filesystem
> unmountable, but I have literally dozens of cases where following our
> documented process [1] fixes such problems and ZERO where it does not.
> 
> Therefore there claims of dataloss are not valid and this second issue could
> be considered Major (because of the disruption) but not Critical
> 

I reported this problem in 2016 at the opensuse-factory mailing list:

https://lists.opensuse.org/opensuse-factory/2016-09/msg00130.html

Back in the day, this was affecting a server (with HDDs) and my laptop (with
SSDs). Unfortunately, I had to reinstall all my server once because a power
failure during those high loads corrupted the filesystem and I could not
managed to recover it... However, it was 2 years ago and things could have been
improved. I have never seen this anymore because my first action after
installing openSUSE is to disable qgroups now.

(In reply to Gabor Katona from comment #52)
> Currently BTRFS is experimental, the sooner you accept it the faster you
> provide a solution: SKIP BTRFS for opensuse.

I do not agree. BTRFS has been running here without any problems for 2 years,
since I disable qgroups. What should be considered experimental (as warned here
https://lists.opensuse.org/opensuse-factory/2016-09/msg00032.html ) is quotas /
qgroups. I have no idea if this has been improved, but since people are seeing
the problem, I guess it is still the same.