running IOR on non shared filesystem

[puneet336]

Hi, I am trying to run IOR benchmark using - mpirun -np 256 -ppn 128 $PWD/ior -t 4m -b 16m -F -C

and i am getting following issue -

ior ERROR: open64("testFile.00000128", 2) failed, errno 2, No such file or directory (aiori-POSIX.c:473)
ior ERROR: open64("testFile.00000161", 2) failed, errno 2, No such file or directory (aiori-POSIX.c:473)

I am trying to run the benchmark from local file system only ( /var/tmp), i.e. file created on one node will not be accessible to second node.

Are there any ior specific options which i need to add or remove to make IOR work on non shared filesystems?. please advice.

[adilger]

IOR is intended to test the performance of shared parallel filesystems. There are other benchmarks like "fio" or "iozone" that can be used to test local filesystems.

What is your goal here?

[JulianKunkel]

Hi, actually, that should work, just do not use -C flag: mpirun -np 256 -ppn 128 $PWD/ior -t 4m -b 16m -F That way each process reads the own data back...

[puneet336]

Thank you @JulianKunkel , the run is now working . But another issue which i am getting is that Warning messages are showing up on terminal. Is there a way to disable these warning messages or a possible workaround by adding few parameters?

access    bw(MiB/s)  IOPS       Latency(s)  block(KiB) xfer(KiB)  open(s)    wr/rd(s)   close(s)   total(s)   iter
------    ---------  ----       ----------  ---------- ---------  --------   --------   --------   --------   ----
ior WARNING: inconsistent file size by different tasks.
WARNING: Expected aggregate file size       = 268435456.
WARNING: Stat() of aggregate file size      = 134217728.
WARNING: Using actual aggregate bytes moved = 268435456.
write     1045.15    1045.58    0.000966    1024.00    1024.00    0.207309   0.244841   0.234031   0.244941   0
ior WARNING: inconsistent file size by different tasks.
WARNING: Expected aggregate file size       = 268435456.
WARNING: Stat() of aggregate file size      = 134217728.
WARNING: Using actual aggregate bytes moved = 268435456.
read      1204.43    1204.75    0.004968    1024.00    1024.00    0.207301   0.212492   0.211409   0.212549   0
remove    -          -          -           -          -          -          -          -          0.015359   0
Max Write: 1045.15 MiB/sec (1095.92 MB/sec)
Max Read:  1204.43 MiB/sec (1262.93 MB/sec)

Summary of all tests:
Operation   Max(MiB)   Min(MiB)  Mean(MiB)     StdDev   Max(OPs)   Min(OPs)  Mean(OPs)     StdDev    Mean(s) Stonewall(s) Stonewall(MiB) Test# #Tasks tPN reps fPP reord reordoff reordrand seed segcnt   blksiz    xsize aggs(MiB)   API RefNum
write        1045.15    1045.15    1045.15       0.00    1045.15    1045.15    1045.15       0.00    0.24494         NA            NA     0    256 128    1   0     0        1         0    0      1  1048576  1048576     256.0 POSIX      0
read         1204.43    1204.43    1204.43       0.00    1204.43    1204.43    1204.43       0.00    0.21255         NA            NA     0    256 128    1   0     0        1         0    0      1  1048576  1048576     256.0 POSIX      0
Finished            : Sun Jul 10 23:57:57 2022
MESSAGE: terminated

@adilger thank you for the reply. I am adding a wrapper script around few filesystem benchmarks. I plan to add an option to specify paths (shared or local). I was exploring if there is a way to run the benchmark incase local filesystem is specified.

[JulianKunkel]

At the moment, there is no flag to suppress these. Arguably, in this specific case, the warnings could be adjusted in the code, however, I think it is fine as they remind us, that this isn't the typical use case.

[JulianKunkel]

I suppose this issue is closed! Thanks.