Hi, In addition, some log was generated by KVM processes: > qemu: terminating on signal 15 from pid 2827 > osdc/ObjectCacher.cc: In function 'ObjectCacher::~ObjectCacher()' > thread 7f265a77da80 time 2016-11-23 17:26:24.237542 > osdc/ObjectCacher.cc: 551: FAILED assert(i->empty()) > ceph version 0.94.8 (838cd35201e4fe1339e16d987cc33e873524af90) > 1: (()+0x15b8ab) [0x7f2649afc8ab] > 2: (()+0x38cfdd) [0x7f2649d2dfdd] > 3: (()+0x57406) [0x7f26499f8406] > 4: (()+0x7e3cd) [0x7f2649a1f3cd] > 5: (rbd_close()+0x9) [0x7f26499dd529] > 6: (()+0x2c12) [0x7f264bf70c12] > 7: (bdrv_close()+0x80) [0x565063a61b90] > 8: (bdrv_unref()+0x97) [0x565063a61e27] > 9: (bdrv_close()+0x155) [0x565063a61c65] > 10: (bdrv_close_all()+0x3c) [0x565063a61d5c] > 11: (main()+0x418f) [0x5650637bde2f] > 12: (__libc_start_main()+0xf5) [0x7f2655297f45] > 13: (()+0xfbaa1) [0x5650637c1aa1] > NOTE: a copy of the executable, or `objdump -rdS <executable>` is > needed to interpret this. > terminate called after throwing an instance of 'ceph::FailedAssertion' Hope it helps. Cheers, Kees On 24-11-16 13:06, Kees Meijs wrote: > Could someone please give some pointers in how to debug this? Log files > seem a little "voidy" on the matter, I'm afraid. _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |