Thanks Colin,
For your information, I ran a loop test[1] on each of stress-ng tags
since V0.12.00, with 100 times lockofd run and see the return value.
This issue starts to be seen since V0.12.09 (or maybe early because the
reprudce chance is very low). Full console log is attached for your
information.
--
#!/bin/bash
for i in `cat gittag.txt`; do
echo ==== $i ====
cd /home/ubuntu/stress-ng
make clean
git reset --hard
git checkout $i
make clean
make
cd /home/ubuntu
for j in `seq 1 100`; do
./stress-ng/stress-ng --lockofd 0 -t 240
echo == $? ==
done
done
** Attachment added: "screenlog.0.gz"
https://bugs.launchpad.net/stress-ng/+bug/1999731/+attachment/5652313/+files/screenlog.0.gz
--
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:
Invalid
Status in stress-ng package in Ubuntu:
Fix Released
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
