Roger Heflin (rogerheflin@xxxxxxxxx) wrote on Mon, Oct 30, 2023 at 01:14:49PM -03: > look at SAR -d output for all the disks in the raid6. It may be a > disk issue (though I suspect not given the 100% cpu show in raid). > > Clearly something very expensive/deadlockish is happening because of > the raid having to rebuild the data from the missing disk, not sure > what could be wrong with it. This is very similar to what I complained some 3 months ago. For me it happens with an array in normal state. sar shows no disk activity yet there are no writes to the array (reads happen normally) and the flushd thread uses 100% cpu. For the latest 6.5.* I can reliably reproduce it with % xzcat linux-6.5.tar.xz | tar x -f - This leaves the machine with ~1.5GB of dirty pages (as reported by /proc/meminfo) that it never manages to write to the array. I've waited for several hours to no avail. After a reboot the kernel tree had only about 220MB instead of ~1.5GB...
