New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qa/tasks/rbd_fio: bump default fio version to 2.21 #16656

Merged
merged 1 commit into from Aug 1, 2017

Conversation

Projects
None yet
2 participants
@idryomov
Contributor

idryomov commented Jul 28, 2017

I'm seeing sporadic single thread deadlocks on fio stat_mutex during krbd
thrash runs:

(gdb) info threads
Id Target Id Frame

  • 1 Thread 0x7f89ee730740 (LWP 15604) 0x00007f89ed9f41bd in __lll_lock_wait () from /lib64/libpthread.so.0
    (gdb) bt
    #0 0x00007f89ed9f41bd in __lll_lock_wait () from /lib64/libpthread.so.0
    #1 0x00007f89ed9f17b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
    #2 0x00000000004429b9 in fio_mutex_down (mutex=0x7f89ee72d000) at mutex.c:170
    #3 0x0000000000459704 in thread_main (data=) at backend.c:1639
    #4 0x000000000045b013 in fork_main (offset=0, shmid=, sk_out=0x0) at backend.c:1778
    #5 run_threads (sk_out=sk_out@entry=0x0) at backend.c:2195
    #6 0x000000000045b47f in fio_backend (sk_out=sk_out@entry=0x0) at backend.c:2400
    #7 0x000000000040cb0c in main (argc=2, argv=0x7fffad3e3888, envp=) at fio.c:63
    (gdb) up 2
    170 pthread_cond_wait(&mutex->cond, &mutex->lock);
    (gdb) p mutex.lock.__data.__owner
    $1 = 15604

Upgrading to 2.21 seems to make these go away.

Signed-off-by: Ilya Dryomov idryomov@gmail.com

qa/tasks/rbd_fio: bump default fio version to 2.21
I'm seeing sporadic single thread deadlocks on fio stat_mutex during krbd
thrash runs:

  (gdb) info threads
    Id   Target Id         Frame
  * 1    Thread 0x7f89ee730740 (LWP 15604) 0x00007f89ed9f41bd in __lll_lock_wait () from /lib64/libpthread.so.0
  (gdb) bt
  #0  0x00007f89ed9f41bd in __lll_lock_wait () from /lib64/libpthread.so.0
  #1  0x00007f89ed9f17b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  #2  0x00000000004429b9 in fio_mutex_down (mutex=0x7f89ee72d000) at mutex.c:170
  #3  0x0000000000459704 in thread_main (data=<optimized out>) at backend.c:1639
  #4  0x000000000045b013 in fork_main (offset=0, shmid=<optimized out>, sk_out=0x0) at backend.c:1778
  #5  run_threads (sk_out=sk_out@entry=0x0) at backend.c:2195
  #6  0x000000000045b47f in fio_backend (sk_out=sk_out@entry=0x0) at backend.c:2400
  #7  0x000000000040cb0c in main (argc=2, argv=0x7fffad3e3888, envp=<optimized out>) at fio.c:63
  (gdb) up 2
  170                     pthread_cond_wait(&mutex->cond, &mutex->lock);
  (gdb) p mutex.lock.__data.__owner
  $1 = 15604

Upgrading to 2.21 seems to make these go away.

Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
@dillaman

lgtm

@dillaman dillaman merged commit 2589f57 into ceph:master Aug 1, 2017

4 checks passed

Signed-off-by all commits in this PR are signed
Details
Unmodified Submodules submodules for project are unmodified
Details
make check make check succeeded
Details
make check (arm64) make check succeeded
Details

@idryomov idryomov deleted the idryomov:wip-qa-newer-fio branch Aug 10, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment