https://bugzilla.suse.com/show_bug.cgi?id=1214004 https://bugzilla.suse.com/show_bug.cgi?id=1214004#c5 --- Comment #5 from Coly Li <colyli@suse.com> --- (In reply to Ulrich Windl from comment #4)
(In reply to Hannes Reinecke from comment #3)
According to the BIOS message on booting the RAID was is "verify mode", so nothing actually needed writing or fixing unless there was a mismatch detected. However I don't know how MD-RAID actually handles that.
What could be done?
If it's possible to detect that kind of problem (read stalls obviously), the default speed_limit_max could be reduced automatically until the situation improves. Obviously such mechanism should be "located near MD-RAID activation".
Being practically unable to work with the system for hours cannot be the solution (I'm aware that a "change bitmap" on the array would be the best solution, but the hardware doesn't support that AFAIK)
Recently it was reported that an upstream issue had similar behavior as you described. This issue was fixed in recent openSUSE Leap 15.6 kernel (leap 15.5 is on the way). Note: the fix comes after openSUSE Leap 15.6 released, please download the latest installation iso. -- You are receiving this mail because: You are on the CC list for the bug.