On 9 June 2016 at 22:58, Jeff Furlong <jeff.furlong@xxxxxxxx> wrote: > > Using the latest version from git, I am getting a signal 11 error when running some workloads. It may be that workloads fail when we wrap around the device capacity (e.g. runtime and time_based). See below example parameters: > > # fio --name=test_job --ioengine=libaio --direct=1 --rw=write --iodepth=32 --size=100% --numjobs=1 --bs=1m --filename=/dev/nvme0n1 --group_reporting --write_bw_log=test_job --write_iops_log=test_job --write_lat_log=test_job --log_avg_msec=1000 --disable_lat=0 --disable_clat=0 --disable_slat=0 --runtime=1500s --time_based --ramp_time=5s --output=test_job > > fio-2.11-17-ga275 > Starting 1 process > fio: pid=145763, got signal=11 Could you run fio under gdb ( gdb ./fio run --name=test_job --ioengine=libaio etc. ) and when it crashes get a backtrace with thread apply all bt ? -- 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
