Return value 7 is "EXIT_METRICS_UNTRUSTWORTHY", this may mean the
stressor may have been killed manually and/or it terminated abruptly
causing it to be unable to store the bogo/ops metrics in a shared memory
segment reliably.
Only two commits have changed in the lockofd stressor since Aug 2022:
commit 6274835de403ec310b20d2771ccf21a523b94cec
Author: Colin Ian King <colin.i.k...@gmail.com>
Date: Tue Nov 15 19:57:28 2022 +0000
stress-*: rename stress_not_implemented to stress_unimplemented
Signed-off-by: Colin Ian King <colin.i.k...@gmail.com>
commit 7ccc5fe9d18b7d467e8279c0a791df6453e5a451
Author: Colin Ian King <colin.i.k...@gmail.com>
Date: Tue Nov 15 19:47:32 2022 +0000
stress-*: add more explanation about stressors being unimplmented
It's useful for users to have some idea why a stressor is not implemented
or useable on the various systems that stress-ng can build on.
Signed-off-by: Colin Ian King <colin.i.k...@gmail.com>
These commits didn't change the functionality of stress-ng's lockofd
stressor from what I can see.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999731
Title:
disk stress test failing with code 7
Status in Stress-ng:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in stress-ng package in Ubuntu:
In Progress
Bug description:
Since mid of November we see lots of disk stress test failing with
multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them
are with lockofd stressor and system are still alive after stress
test.
05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds...
** stress-ng exited with code 7
To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1999731/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
