always crashes with fstat stressor
Hi there,
always see hard resets (no logs, no messages) on different machines if they run the fstat stressor (even one stressor is enough). Cause I see this behaviour on different systems I assume that this is not hardware error but a may be a bsic problem of the stressor itself, could it? MOst of the systems use a RAID controller, but different models, stress-ng is running on RAID volumes.
Or any ideas how to "debug" what's going on then during a fstat run? Verbosity does not show me any hint...
Thank you in advance
Martin
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Ubuntu stress-ng Edit question
- Assignee:
- No assignee Edit question
- Last query:
- 2015-09-08
- Last reply:
- 2015-09-10
Colin Ian King (colin-king) said : | #1 |
The fstat stressor is basically just stat'ing a load of files in /dev, so it looks like an open()... fstat() ... close() or a stat() on a /dev/ entry is causing the kernel some issues. Are you running stress-ng as root or not?
One way to see what is happening is to log in remotely and run strace on stress-ng, this will capture the moment when a particular /dev is accessed.. So run:
strace -f stress-ng --fstat 1
and see where it hangs. This looks like stress-ng has found a kernel bug, so I'd be interested in seeing what happens, and which kernel you are running on.
Colin Ian King (colin-king) said : | #2 |
Hi mpcore, do you following this up in bug https:/
Can you help with this problem?
Provide an answer of your own, or ask mpcore for more information if necessary.