I do not believe that the error is Unraid specific (and that it is actually a Linux kernel issue), it is just that the type of workloads frequently run on Unraid servers seem prone to triggering it. We should see a fix incorporated into the 6.9 Unraid release for which the first RC is reported to be imminent.