Ok after some debugging I found the issue with the h5bench_e3sm. It is the way path was constructed for e3sm dataset Once I fixed that I could run it. It might be useful to mention that in the documentation to copy the dataset correctly.
However for the metadata I think the executable its running its incorrect. It is using h5bench_exerciser instead of h5bench_hdf5_iotest
2022-10-04 09:45:49,783 h5bench - INFO - h5bench [write] - Complete
2022-10-04 09:45:49,783 h5bench - INFO - h5bench [metadata] - Starting
2022-10-04 09:45:49,784 h5bench - INFO - h5bench [metadata] - DIR: /p/gpfs1/iopp/temp/h5bench/90bd7c67/
2022-10-04 09:45:49,785 h5bench - INFO - Parallel setup: jsrun -r 1 -a 4 -c 4
2022-10-04 09:45:49,787 h5bench - INFO - jsrun -r 1 -a 4 -c 4 h5bench_exerciser /p/gpfs1/iopp/temp/h5bench/90bd7c67/hdf5_iotest.ini
2022-10-04 09:45:50,130 h5bench - ERROR - Return: 255 (check /p/gpfs1/iopp/temp/h5bench/90bd7c67/stderr for detailed log)
2022-10-04 09:45:50,130 h5bench - INFO - Runtime: 0.3438661 seconds (elapsed time, includes allocation wait time)
2022-10-04 09:45:50,130 h5bench - INFO - h5bench [metadata] - Complete
2022-10-04 09:45:50,130 h5bench - INFO - Finishing h5bench Suite
Also, make sure ASYNC documentation is reported correctly for this benchmark:
I think setting the “ASYNC_MODE" has been deprecated, but the documentation is not updated.
Can you try setting the “MODE" parameter with “SYNC” instead of setting the ASYNC_MODE?
Bug Report
Also, make sure ASYNC documentation is reported correctly for this benchmark: