I found the issue I was using a tiny base centos some how libaio-devel install and recompile fixed it + print_config 'Linux AIO support' yes + printf '%-30s%s\n' 'Linux AIO support' yes Linux AIO support yes ty all as always! On Mon, Sep 18, 2017 at 2:26 PM, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: > Hi, > > On 18 September 2017 at 09:58, Udi-Yehuda Tamar <udi@xxxxxxxxxxxx> wrote: >> I just retest it and in 2.99 all is working but v3 not >> please elaborate >> >> On Mon, Sep 18, 2017 at 11:54 AM, Udi-Yehuda Tamar <udi@xxxxxxxxxxxx> wrote: >>> >>> After moving from 2.99 to v3.0.61 I got: >>> >>> DEBUG: ROUND PARAMS: job=8 ioDepth=1 blockSize=4k rwmixread=0 ioEngine=libaio >>> ERROR: fio: engine libaio not loadable >>> ERROR: fio: failed to load engine >>> DEBUG: fio: file:ioengines.c:91, func=dlopen, error=libaio: cannot >>> open shared object file: No such file or directory >>> >>> libaio and libaio-devel are both installed on latest , any Idea ? > > It sounds like your fio has been compiled without libaio support and > you can confirm this by doing this: > path/to/fio/fio --enghelp > > Can you have whoever is compiling fio give you the output of doing > bash -x ./configure 2>&1 | grep -B 20 'Linux AIO support' > so you can post it here? > > -- > Sitsofe | http://sucs.org/~sits/ -- Thanks, Udi-Yehuda Tamar. -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html