thx, that worked. -ben ----- Original Message ----- > From: "Jens Axboe" <axboe@xxxxxxxxx> > To: "Ben England" <bengland@xxxxxxxxxx>, fio@xxxxxxxxxxxxxxx > Cc: "Tim Wilkinson" <twilkins@xxxxxxxxxx> > Sent: Tuesday, May 24, 2016 8:41:42 PM > Subject: Re: assert failing with latency log > > On 05/24/2016 03:40 PM, Ben England wrote: > > If I run this fio jobfile with absolute latest upstream code: > > > > [global] > > directory=/var/tmp > > > > [randreads] > > direct=1 > > rate_iops=1000 > > size=512m > > ioengine=sync > > bs=4k > > rw=randread > > filename=ben.dd > > runtime=30 > > write_lat_log=foo > > > > It fails with > > > > fio: stat.c:1988: get_cur_log: Assertion `iolog->pending->nr_samples < > > iolog->pending->max_samples' failed. > > > > But if I take out the "write_lat_log=foo" line, it succeeds. The assertion > > seems to be in the code path for latency logs, right? Anyone else seen > > this? > > Gah, that's my bad, I broke sync IO engines with logging. I pushed a fix: > > http://git.kernel.dk/cgit/fio/commit/?id=cf2c8d5260c9676964854e79382cba3eb498fd2e > > I'll tag a new version as well, this is pretty unfortunate. > > -- > Jens Axboe > > -- 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
