I am running with spdk 18.10.3, and crashing during delete_nvmf_subsystem.
This happens pretty consistently (every 2-3 attempts) when I do the delete while the
initiator is still connected.
I saw that bug #235 has the same stack trace as I am seeing, but I already have the fix.
I am digging into this, but would be glad to get some pointers as to where to start
looking, or more specifically, how did you know to look into the lib/nvmf controller code
according to this error.
This is my stack:
#0 0x00007f338ed46495 in raise () from /lib64/libc.so.6
#1 0x00007f338ed47c75 in abort () from /lib64/libc.so.6
#2 0x00007f338ed843a7 in __libc_message () from /lib64/libc.so.6
#3 0x00007f338ed89dee in malloc_printerr () from /lib64/libc.so.6
#4 0x00007f338ed8cc80 in _int_free () from /lib64/libc.so.6
#5 0x000000000047ca07 in _spdk_event_queue_run_batch (arg=0x7f32dc008640) at
#6 _spdk_reactor_run (arg=0x7f32dc008640) at reactor.c:502
#7 0x000000000047ccac in spdk_reactors_start () at reactor.c:677
#8 0x00000000007a942e in km_spdk_target_reactor_thread (arg=0x1da4b160) at
#9 0x00000000007b28e1 in km_thread_log (ctxt=0x7f32e0001ea0) at km_thread_pthreads.c:79
#10 0x00007f338fb85aa1 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f338edfcbcd in clone () from /lib64/libc.so.6
I will open a bug on github for this once I collect all the information.
Show replies by date