Hi folks, On 2024-09-21 09:58:55, Harald Dunkel wrote:
NeilBrown wrote:We can guess though. It isn't waiting for a lock - that would show in the above list - so it might be waiting for a wakeup, or might be spinning. The only wake-up I can imagine is in one of the memory-allocation calls, but if the system were running out of memory we would probably see messages about that.I have seen something like this. I am running NFS inside a container, using legacy cgroup. When it got stuck it claimed I cannot login into the container due to out of memory. When it happens again, I can send you the exact error message. The next hung nfsd is overdue, anyway.
my NFS server got stuck again last night. Unfortunately the service was recovered by a colleague, so I had no chance to check the memory. Attached you can find the log files of both nfs container and LXC server, with /proc/sys/kernel/hung_task_all_cpu_backtrace set to 1. I dropped the kernel mailing list from this reply, due to large attachments. Hopefully this was OK? Hope this helps. Please mail if I can help Harri
Attachment:
log.nfs01.txt.gz
Description: application/gzip
Attachment:
log.nasl006.txt.gz
Description: application/gzip
