I finally caught this happening while I had "lockstat sleep 1" running
in a loop, the output looks like:
https://gist.github.com/swills/a2a20c2a4296a4c596ec7f329fb945ab
And top looks like this:
https://gist.github.com/swills/6e749313e52679224adec91d4841ad83
Also noticed that there are actually 2 threads of pid 17
[zfskern{txg_thread_enter}] which are reporting 57% and 42% of disk IO,
everything else is idle as far as IO. The system is not totally
unresponsive, processes that don't need IO are working, but anything
that needs IO hangs. Perhaps it's a hardware issue, but I can't find any
other evidence of it. Any ideas?
Steve
On 04/24/2018 19:30, Steve Wills wrote:
Hi,
Recently on multiple systems running CURRENT, I've been seeing the
system become unresponsive. Leaving top(1) running has lead me to notice
that when this happens, the system is still responding to ping and top
over ssh is still working, but no new processes can start and switching
to other tasks doesn't work. In top, I do see pid 17,
[zfskern{txg_thread_enter}] monopolizing both CPU usage and disk IO. Any
ideas how to troubleshoot this? It doesn't appear to be a hardware issue.
Steve
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
