Re: io_u->flags & IO_U_F_FLIGHT failed errors when using libaio

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Feb 6, 2015 at 11:03 PM, Lakshmi <sendtold@xxxxxxxxx> wrote:
> Hi Jens,
>    I have a job file that looks like below and it keeps giving errors
> like attached in screen shot. I am using fio-2.2.4
>
> cmd="$FIO --name=test  --group_reporting=1 --ioengine=libaio
> --invalidate=1 --iodepth=32 --bs=4K --filename=/dev/sde --rw=randread
> --direct=1 --buffered=0 --time_based --runtime=300 --numjobs=64"

While t's perfectly legal, you're setting a rather large total io
depth for a single device (32 by 64), but otherwise the job seems fine
(and runs fine against a regular file with fio 2.2.5 here). If the bug
persists, you might want to rerun it under gdb to get a clue (such as
to print out the io_u that triggers the assert).

Regards,
Andrey

>
> Any idea what is causing this?
>
> Thanks
> LD
--
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




[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux