Actually it seems that bug is in the blktrace (not blkparse) when using piped mode and ncpu > 1. Overriding ncpu to 1 solves this problem. 2016-09-28 18:07 GMT+05:00 Alexey Egorov <alex.only.d@xxxxxxxxx>: > More info on this: > > I can observe this bug only when piping blktrace output to blkparse. > When I use temporary files all seems to be OK. > Also, I found that this particular commit causes this bug: > http://git.kernel.org/cgit/linux/kernel/git/axboe/blktrace.git/commit/?id=9bf422b17cb2330f94376f8ca82a6e6cc496f9a3 > > > 2016-09-28 7:56 GMT+05:00 Alexey Egorov <alex.only.d@xxxxxxxxx>: >> Hello, >> >> I'm getting multiple entries with unordered timestamps using version >> 1.1.0 of blkparse: >> >> $ verify_blkparse test.out >> ... >> Events 184855: 127 unordered, 57773 aliases >> >> Any chance it would be fixed? For now I'm going to use 1.0.1, which >> doesn't have this problem. >> >> Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-btrace" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
