Hi, Could you please enable rocksdb logging and get the logs, if you are hitting the issue consistently? Thanks, Varada On Saturday 03 December 2016 06:08 PM, 马建朋 wrote: > Hi All > Based v11.0.2 i did write-test and always met this bug as followings: > -1> 2016-12-03 11:47:34.897412 7fa4207fd700 -1 rocksdb: > submit_transaction error: NotFound: code = 1 Rocksdb transaction: > Put( Prefix = M key = > 0x000000000000079c'.0000000272.00000000000000075338' Value size = 182) > Put( Prefix = M key = 0x000000000000079c'._epoch' Value size = 4) > Put( Prefix = M key = 0x000000000000079c'._info' Value size = 855) > Put( Prefix = O key = > 0x7f8000000000000001600ab4'%!rbd_data.5f126b8b4567.000000000000233e!='0xfffffffffffffffeffffffffffffffff > Value size = 526) > Put( Prefix = L key = 0x0000000004be661a Value size = 4138) > 0> 2016-12-03 11:47:34.899063 7fa4207fd700 -1 > /root/ceph/src/os/bluestore/BlueStore.cc: In function 'void > BlueStore::_kv_sync_thread()' thread 7fa4207fd700 time 2016-12-03 > 11:47:34.897441 > /root/ceph/src/os/bluestore/BlueStore.cc: 6484: FAILED assert(r == 0) > > ceph version v11.0.2 (697fe64f9f106252c49a2c4fe4d79aea29363be7) > 1: (ceph::__ceph_assert_fail(char const*, char const*, int, char > const*)+0x8b) [0x5651411b675b] > 2: (BlueStore::_kv_sync_thread()+0x1be4) [0x565140f5e404] > 3: (BlueStore::KVSyncThread::entry()+0xd) [0x565140f6bc5d] > 4: (()+0x8182) [0x7fa45c1e8182] > 5: (clone()+0x6d) [0x7fa45ab5547d] > NOTE: a copy of the executable, or `objdump -rdS <executable>` is > needed to interpret this. > > But test the same case on master code, i don't see this bug. > I need help. Thanks very much > > Jianpeng. > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > PLEASE NOTE: The information contained in this electronic mail message is intended only for the use of the designated recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender by telephone or e-mail (as shown above) immediately and destroy any and all copies of this message in your possession (whether hard copies or electronically stored copies). ?韬{.n?????%??檩??w?{.n????u朕?Ф?塄}?财??j:+v?? ? ???2??璀??摺?囤??z夸z罐?+?????w棹f
