Hi, I got some new traces of the stuck fio process. This is 2.1.13: (gdb) bt #0 0x00007f53cbb085bc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x0000000000430339 in fio_mutex_down (mutex=0x7f53c24ce000) at mutex.c:155 #2 0x0000000000411950 in stat_exit () at stat.c:1905 #3 0x000000000044c756 in fio_backend () at backend.c:2094 #4 0x00007f53cb583d1d in __libc_start_main () from /lib64/libc.so.6 #5 0x0000000000409e49 in _start () (gdb) With fio-2.1.13-88-gb2ee7: (gdb) bt #0 0x00007f871e9de22d in pthread_join () from /lib64/libpthread.so.0 #1 0x0000000000411939 in wait_for_status_interval_thread_exit () at stat.c:1939 #2 0x000000000044ce2a in fio_backend () at backend.c:2084 #3 0x00007f871e45cd1d in __libc_start_main () from /lib64/libc.so.6 #4 0x000000000040a529 in _start () (gdb) Regards Michael On Thu, Oct 23, 2014 at 9:01 AM, Jens Axboe <axboe@xxxxxxxxx> wrote: > On 10/23/2014 09:57 AM, Michael Mattsson wrote: >> Hey, >> Have there been any work on this? This is still an issue for me on fio >> 2.1.13. It happens less frequently but I've had two hangs in a sample >> of ~40 runs. > > Try current -git and see if it works better. If not, lets get some new > traces and we'll get this fixed up. > > -- > 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
