On 12 September 2017 at 00:04, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: > On 10 September 2017 at 03:32, Brandon Schwartz <schwartz.xn@xxxxxxxxx> wrote: >> On Thu, Sep 7, 2017 at 11:22 PM, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: >>> On 8 September 2017 at 06:10, Brandon Schwartz <schwartz.xn@xxxxxxxxx> wrote: >>>> On Thu, Sep 7, 2017 at 10:46 PM, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: >>>>> >>>>> On 8 September 2017 at 01:13, Brandon Schwartz <schwartz.xn@xxxxxxxxx> wrote: >>>>>> >>>>>> Running the following job file with --io_submit_mode=offload set will >>>>>> occasionally give a 'No I/O performed by libaio' error [...] >>> OK this seems to reproduce the problem: >>> >>> ./fio --debug=io --name=zerolenread --size=1M --rw=randread >>> --bs=128k,64k --ioengine=libaio --io_submit_mode=offload >>> --filename=/tmp/zerolenread >> >> I tried digging into the code to see what's going on, but I'm not >> having much luck. Adding --norandommap to the job file will >> at least get around the error/zero length transfer. > > I'd file this as an issue on github so it doesn't completely slip > through the net. Looks like this has been solved by https://github.com/axboe/fio/commit/956e60eade2bddb8aadfb54b58030e0b88fd03b2 ... -- Sitsofe | http://sucs.org/~sits/ -- 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
