On 1 November 2016 at 03:12, Jaze Lee <jazeltq@xxxxxxxxx> wrote: > Hello, > I found that when rate_iops used with write_lat_log， it will be > high probability > that the fio will assert. The below is the core dump. > > (gdb) bt > #0 0x00007f3c3ccd25f7 in raise () from /lib64/libc.so.6 > #1 0x00007f3c3ccd3ce8 in abort () from /lib64/libc.so.6 > #2 0x00007f3c3cccb566 in __assert_fail_base () from /lib64/libc.so.6 > #3 0x00007f3c3cccb612 in __assert_fail () from /lib64/libc.so.6 > #4 0x000000000042249c in get_cur_log (iolog=0x7f3c390bb8b0) at stat.c:2004 > #5 __add_log_sample (iolog=iolog@entry=0x7f3c390bb8b0, > val=val@entry=1, ddir=ddir@entry=DDIR_WRITE, bs=bs@entry=4096, t=1024, > offset=offset@entry=972521472) > at stat.c:2019 Could you include the job file / command line that reproduces the issue and the version of fio you were using? -- 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
