stress-ng --hdd arguments documentation unclear #158
Comments
|
On 11/11/2021 11:22, Shankar Daruga wrote:
Hello, I'm stress testing my Disk IO using the below hdd command :
stress-ng --hdd 3 --hdd-write-size 512 --hdd-bytes 6g --hdd-opts
direct,sync,wr-rnd,rd-rnd --timeout 0 (This works and results in
successful exit)
However, when I change the workers number (-hdd) to 5, it fails as given
below:
***@***.***:~$ stress-ng --hdd 5 --hdd-write-size 512
--hdd-bytes 256g --hdd-opts direct,sync,wr-rnd,rd-rnd --timeout 0 --verbose
stress-ng: debug: [12316] 2 processors online, 2 processors configured
stress-ng: info: [12316] dispatching hogs: 5 hdd
stress-ng: debug: [12316] cache allocate: default cache size: 36608K
stress-ng: debug: [12316] starting stressors
stress-ng: debug: [12317] stress-ng-hdd: started [12317] (instance 0)
stress-ng: fail: [12317] stress-ng-hdd: write failed, errno=22 (Invalid
argument)
stress-ng: debug: [12316] 5 stressors spawned
stress-ng: debug: [12317] stress-ng-hdd: exited [12317] (instance 0)
stress-ng: debug: [12319] stress-ng-hdd: started [12319] (instance 2)
stress-ng: fail: [12319] stress-ng-hdd: write failed, errno=22 (Invalid
argument)
stress-ng: debug: [12319] stress-ng-hdd: exited [12319] (instance 2)
stress-ng: debug: [12318] stress-ng-hdd: started [12318] (instance 1)
stress-ng: error: [12316] process 12317 (stress-ng-hdd) terminated with
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12316] process [12317] terminated
stress-ng: fail: [12318] stress-ng-hdd: write failed, errno=22 (Invalid
argument)
stress-ng: debug: [12320] stress-ng-hdd: started [12320] (instance 3)
stress-ng: debug: [12318] stress-ng-hdd: exited [12318] (instance 1)
stress-ng: fail: [12320] stress-ng-hdd: write failed, errno=22 (Invalid
argument)
stress-ng: error: [12316] process 12318 (stress-ng-hdd) terminated with
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12316] process [12318] terminated
stress-ng: error: [12316] process 12319 (stress-ng-hdd) terminated with
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12316] process [12319] terminated
stress-ng: debug: [12321] stress-ng-hdd: started [12321] (instance 4)
stress-ng: debug: [12320] stress-ng-hdd: exited [12320] (instance 3)
stress-ng: fail: [12321] stress-ng-hdd: write failed, errno=22 (Invalid
argument)
stress-ng: debug: [12321] stress-ng-hdd: exited [12321] (instance 4)
stress-ng: error: [12316] process 12320 (stress-ng-hdd) terminated with
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12316] process [12320] terminated
stress-ng: error: [12316] process 12321 (stress-ng-hdd) terminated with
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12316] process [12321] terminated
stress-ng: info: [12316] unsuccessful run completed in 0.00s
At first, I thought this could be a resource issue, but I have tried
giving the same command with -hdd as 16 (which is more than 5), this
seems to work !!
After multiple trials of running this program and with varied value of
-hdd and -hdd-bytes, there seems to be a relation between -hdd and
-hdd-bytes arguments, what I have observed is that if -hdd is a
divisible by -hdd-bytes, the program seems to run okay and when that
isn't the case, it doesn't seem to run at all, failing with errno 22
invalid argument (just as above).
I have tried to read the source code but couldn't get what could be
causing the issue.
This bug is due to a 512 byte rounding issue with odd number of
stressors when doing direct I/O. I'll send a fix when I have a free
moment at lunch time today.
…
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#158>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACHCRL3TWKEEEMU6EOLF6JTULOROPANCNFSM5H2G6RBQ>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Thanks for reporting this. Fix committed, commit 9bbe45d - please test and verify this addresses the issue. |
|
Tested and it is working now. Thank you. May I know when the build will be updated in the ubuntu archives? |
|
On 15/11/2021 06:56, Shankar Daruga wrote:
Tested and it is working now. Thank you. May I know when the build will
be updated in the ubuntu archives?
For which release do you require the fix for?
I'll be doing a new upload for the current latest stress-ng at the end
of this month.
Colin
…
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#158 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACHCRL7EHQFMHBTQCQVKTK3UMCVJLANCNFSM5H2G6RBQ>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
I'm looking for releases for OSes Ubuntu 16.04-LTS and Ubuntu 18.04-LTS |
|
On 15/11/2021 09:37, Shankar Daruga wrote:
I'm looking for releases for OSes Ubuntu 16.04-LTS and Ubuntu 18.04-LTS
OK, I'll do a backport of the fixes and get them through the
Stable-Release Update (SRU) process - but this may take a few weeks to
complete as the SRU process requires at least a week or two to chug
through the process.
Colin
…
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#158 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACHCRL36QEHY7EBUKKWFZ4LUMDIGHANCNFSM5H2G6RBQ>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
See: https://bugs.launchpad.net/bugs/1951152 - SRU for impish, hirsute, focal, bionic. Older releases are too large a delta to easily SRU for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I'm stress testing my Disk IO using the below hdd command :
stress-ng --hdd 3 --hdd-write-size 512 --hdd-bytes 6g --hdd-opts direct,sync,wr-rnd,rd-rnd --timeout 0 (This works and results in successful exit)
However, when I change the workers number (-hdd) to 5, it fails as given below:
azureuser@linuxTestUbuntu:~$ stress-ng --hdd 5 --hdd-write-size 512 --hdd-bytes 256g --hdd-opts direct,sync,wr-rnd,rd-rnd --timeout 0 --verbose
stress-ng: debug: [12316] 2 processors online, 2 processors configured
stress-ng: info: [12316] dispatching hogs: 5 hdd
stress-ng: debug: [12316] cache allocate: default cache size: 36608K
stress-ng: debug: [12316] starting stressors
stress-ng: debug: [12317] stress-ng-hdd: started [12317] (instance 0)
stress-ng: fail: [12317] stress-ng-hdd: write failed, errno=22 (Invalid argument)
stress-ng: debug: [12316] 5 stressors spawned
stress-ng: debug: [12317] stress-ng-hdd: exited [12317] (instance 0)
stress-ng: debug: [12319] stress-ng-hdd: started [12319] (instance 2)
stress-ng: fail: [12319] stress-ng-hdd: write failed, errno=22 (Invalid argument)
stress-ng: debug: [12319] stress-ng-hdd: exited [12319] (instance 2)
stress-ng: debug: [12318] stress-ng-hdd: started [12318] (instance 1)
stress-ng: error: [12316] process 12317 (stress-ng-hdd) terminated with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12316] process [12317] terminated
stress-ng: fail: [12318] stress-ng-hdd: write failed, errno=22 (Invalid argument)
stress-ng: debug: [12320] stress-ng-hdd: started [12320] (instance 3)
stress-ng: debug: [12318] stress-ng-hdd: exited [12318] (instance 1)
stress-ng: fail: [12320] stress-ng-hdd: write failed, errno=22 (Invalid argument)
stress-ng: error: [12316] process 12318 (stress-ng-hdd) terminated with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12316] process [12318] terminated
stress-ng: error: [12316] process 12319 (stress-ng-hdd) terminated with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12316] process [12319] terminated
stress-ng: debug: [12321] stress-ng-hdd: started [12321] (instance 4)
stress-ng: debug: [12320] stress-ng-hdd: exited [12320] (instance 3)
stress-ng: fail: [12321] stress-ng-hdd: write failed, errno=22 (Invalid argument)
stress-ng: debug: [12321] stress-ng-hdd: exited [12321] (instance 4)
stress-ng: error: [12316] process 12320 (stress-ng-hdd) terminated with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12316] process [12320] terminated
stress-ng: error: [12316] process 12321 (stress-ng-hdd) terminated with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [12316] process [12321] terminated
stress-ng: info: [12316] unsuccessful run completed in 0.00s
At first, I thought this could be a resource issue, but I have tried giving the same command with -hdd as 16 (which is more than 5), this seems to work !!
After multiple trials of running this program and with varied value of -hdd and -hdd-bytes, there seems to be a relation between -hdd and -hdd-bytes arguments, what I have observed is that if -hdd is a divisible by -hdd-bytes, the program seems to run okay and when that isn't the case, it doesn't seem to run at all, failing with errno 22 invalid argument (just as above).
I have tried to read the source code but couldn't get what could be causing the issue.
The text was updated successfully, but these errors were encountered: