On Thu, Sep 7, 2017 at 10:46 PM, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: > Hi, > > On 8 September 2017 at 01:13, Brandon Schwartz <schwartz.xn@xxxxxxxxx> wrote: >> Hi, >> >> Running the following job file with --io_submit_mode=offload set will >> occasionally give a 'No I/O performed by libaio' error >> >> Using the latest FIO version (fio-3.0-48-g83a9) >> >> [128k-RR-64k-RW-q1] >> filename=/dev/sdb >> direct=1 >> iodepth=1 >> rw=randrw >> bs=128k,64k >> rwmixread=50 >> ioengine=libaio >> io_submit_mode=offload >> runtime=15m >> >> After a few minutes of running FIO will exit with the following >> message: "No I/O performed by libaio, perhaps try --debug=io option >> for details" >> >> With debug set, I see this near the end of the trace: >> >> io 7720 io complete: io_u 0x55e10ee4abc0: >> off=1304219746304/len=65536/ddir=1io 7720 //dev/sdbio >> 7720 >> io 7720 fill_io_u: io_u 0x55e10ee4abc0: >> off=233107357696/len=0/ddir=0io 7720 //dev/sdbio 7720 > > That's weird - fio tried to submit a zero length read. How big was your device? > It's a 2TB drive -- 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
