Hi all,
I'm trying to run the iozone test on windows, and as it goes, it would seem that 3 runs are performed, after which the process seems to use a lot of CPU but without doing any disk IO (specifically, I let the test run for over 24h since yesterday morning, without the test progressing any further.
Additionally, in order to install iozone, I need to set NO_MD5_CHECKS, since the version for Windows has been bumped to 3.381, also requiring me to edit the "iozone" test file accordingly.
Furthermore, when running the test, I get the following:
...
System Information
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
Hardware:
Processor: Intel Family 6 Model 23 Stepping 10 Intel (1 Core), Disk: 80GB
Software:
OS: Windows NT, Kernel: 6.1 (x86_64)
...
Could this be related, and what might cause this?
This is, btw., a windows install running in a Virtualbox VM.
Best regards,
Sune M?lgaard
I'm trying to run the iozone test on windows, and as it goes, it would seem that 3 runs are performed, after which the process seems to use a lot of CPU but without doing any disk IO (specifically, I let the test run for over 24h since yesterday morning, without the test progressing any further.
Additionally, in order to install iozone, I need to set NO_MD5_CHECKS, since the version for Windows has been bumped to 3.381, also requiring me to edit the "iozone" test file accordingly.
Furthermore, when running the test, I get the following:
...
System Information
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.
Hardware:
Processor: Intel Family 6 Model 23 Stepping 10 Intel (1 Core), Disk: 80GB
Software:
OS: Windows NT, Kernel: 6.1 (x86_64)
...
Could this be related, and what might cause this?
This is, btw., a windows install running in a Virtualbox VM.
Best regards,
Sune M?lgaard
Comment