Re: OpenAFS client softlockup on highly concurrential file-system patterns (100% CPU in kernel mode)

Mark Vitale <[email protected]>
Newsgroups gmane.comp.file-systems.openafs.general
Message-ID <[email protected]>
Ciprian,

> On Nov 19, 2019, at 6:53 AM, Ciprian Dorin Craciun <[email protected]> wrote:
> 
> A few days ago I have encountered a very strange OpenAFS client issue that
> basically exhibits in two ways:
> 
> * either the processes accessing the file-system get "stuck" reading (or
> perhaps opening) the files; (although if one waits "long" enough, sometimes
> those processes will finally complete their job;)  (in this case the CPU
> doesn't go to 100%;)
> 
> * either if one tries to `SIGTERM` the stuck processes, the CPU goes to 100%
> (on multiple cores) in kernel mode;  (again, sometimes if one waits long
> enough, the system settles;)
> 
<snip>
> 
> Any pointers on how to diagnose this?

If you had a true soft lockup, there should be some information in the syslog.
If you don't see anything there, you could try this while the hang is occurring:

# echo t > /proc/sysrq-trigger

This will produce backtraces in the syslog.
Either way, whatever you find in syslog, if you could put it in a paste site of your
choice, then post the link here, that would be helpful.


Regards,
--
Mark Vitale
Sine Nomine Associates
20 Years of Customer Success
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.