Using libaio on current upstream works fine with me.
Assuming your ${IOENGINE} is "libaio", what does below print ?
# fio --enghelp | grep libaio
This part of the message is a bit confusing, as libaio isn't an
external ioengine, i.e. it should be found from the existing ones
rather than having have to dlopen it.
(But we have this logic for backward compatibility reason)
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
2017-09-18 11:54 GMT+03:00 Udi-Yehuda Tamar <udi@xxxxxxxxxxxx>:
> Hello Guys,
>
> I'm using the following config:
>
> [global]
> rw=randrw
> numjobs=${NUMJOBS}
> blocksize=${BLOCKSIZE}
> iodepth=${IODEPTH}
> rwmixread=${RWMIXREAD}
> ioengine=${IOENGINE}
> direct=1
> refill_buffers
> norandommap
> randrepeat=0
> group_reporting
> filesize=5G
> runtime=180
> time_based
>
> [RAND_VOL1]
> filename=${AUTOMATION_MNT_DIR1}/file
>
>
> 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 ?
>
> --
> 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
--
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
