search

thenoizz / stressapptest

Exported from code.google.com/p/stressapptest
Apache License 2.0
0 stars 1 forks source link

disk tests on primary HDD #32

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
(1) stressapptest -s 20 -C 4 --cc_test --stop_on_errors -i 4 -W -M 4096 -f 
/file.1
or
(2) stressapptest -s 20 -C 4 --cc_test --stop_on_errors -i 4 -W -M 4096 -d 
or
(3) stressapptest -s 20 -C 4 --cc_test --stop_on_errors -i 4 -W -M 4096 -d /

What is the expected output? What do you see instead?
(1)
Expect: File Copy: ***value***M at ***value***MB/s
Actual: Process Error: Failed to create file file.1!!
            File Copy: 0.00M at 0.00MB/s
(2)
Expect: Disk: ***value***M at ***value***MB/s
Actual: Disk: 0.00M at 0.00MB/s

(3)
Expect: Disk: ***value***M at ***value***MB/s
Actual: Process Error: Fatal issue encountered. See above logs for details.
            Disk: 0.00M at 0.00MB/s

What version of the product are you using? On what operating system?
stressapptest revision 1.0.6_autoconf, 64 bit binary

Please provide any additional information below.
I am trying to get the speed of the primary hard drive, in other words the 
speed of the drive the os is running on. I do not care if this is by using -d 
or by using -f but I would prefer to use stressapptest as I am already using it 
for some other tests. I am able to get -f info for USB drives I have in the 
system, but not the primary SSD drive. Attached you will find the output of the 
terminal window where I have attempted to get the SSD information.

Original issue reported on code.google.com by shr...@google.com on 10 Apr 2014 at 6:03

Attachments:

GoogleCodeExporter commented 9 years ago 
You are trying to write to /file.1, but you probably don't have permission to 
write to that directory. "-f ~/file.1" should fix this. Two file threads will 
put more load on your ssd so that may be preferable. Storage benchmarking can 
be somewhat complex so the number you get from stressapptest will not give you 
a complete picture. 

I would suggest: 
stressapptest -s 20 --stop_on_errors -W -M 4096 -f ~/file.1 -f ~/file.2

Original comment by nsanders@google.com on 10 Apr 2014 at 8:20