On 12/11/2015 03:01 AM, Andrey Kuzmin wrote:
^Cbs: 1 (f=1): [w(1)] [0.0% done] [0KB/0KB/0KB /s] [0/0/0 iops] [eta 01d:12h:24m:29s] Program received signal SIGINT, Interrupt. 0x00007ffff6b7ff3d in nanosleep () at ../sysdeps/unix/syscall-template.S:81 81 ../sysdeps/unix/syscall-template.S: No such file or directory. (gdb) bt #0 0x00007ffff6b7ff3d in nanosleep () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007ffff6bb14a4 in usleep (useconds=<optimized out>) at ../sysdeps/unix/sysv/linux/usleep.c:32 #2 0x000000000045a7ed in do_usleep (usecs=10000) at backend.c:1951 #3 0x000000000045b33c in run_threads () at backend.c:2216 #4 0x000000000045b6a8 in fio_backend () at backend.c:2333 #5 0x00000000004991cb in main (argc=4, argv=0x7fffffffdda8, envp=0x7fffffffddd0) at fio.c:60
That's not one of the IO threads, that's the main thread. It'll sit and wait in that loop until jobs finish. You'll need the backtrace of one of the stuck IO thread instead, this trace is quite normal and expected of backend.
-- 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
