Project

General

Profile

Actions

Bug #35810

closed

FAILED assert(entries.begin()->version > info.last_update)

Added by Chang Liu over 5 years ago. Updated over 4 years ago.

Status:
Can't reproduce
Priority:
High
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

     0> 2018-09-06 10:53:47.013169 7f73bdffd700 -1 /data/home/jenkins/rpmbuild/BUILD/ceph-12.2.2-700.2.4.2.7/src/osd/PG.cc: In function 'bool PG::append_log_entries_update_missing(mempool::osd_pglog::list<pg_log_entry_t>&, ObjectStore::Transaction&)' thread 7f73bdffd700 time 2018-09-06 10:53:47.008394
/data/home/jenkins/rpmbuild/BUILD/ceph-12.2.2-700.2.4.2.7/src/osd/PG.cc: 5067: FAILED assert(entries.begin()->version > info.last_update)

 ceph version 12.2.2-700.2.4.2.7 (11866d5a4c53837560a70fc8d3a9a3831b86c151) luminous (stable)
 1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x110) [0x7f73daaf3920]
 2: (()+0x59ef4f) [0x7f73da61ff4f]
 3: (PrimaryLogPG::do_update_log_missing(boost::intrusive_ptr<OpRequest>&)+0x68) [0x7f73da6b27c8]
 4: (PrimaryLogPG::do_request(boost::intrusive_ptr<OpRequest>&, ThreadPool::TPHandle&)+0x652) [0x7f73da6d8a52]
 5: (OSD::dequeue_op(boost::intrusive_ptr<PG>, boost::intrusive_ptr<OpRequest>, ThreadPool::TPHandle&)+0x3f9) [0x7f73da562e49]
 6: (PGQueueable::RunVis::operator()(boost::intrusive_ptr<OpRequest> const&)+0x57) [0x7f73da7dbb27]
 7: (OSD::ShardedOpWQ::_process(unsigned int, ceph::heartbeat_handle_d*)+0xfce) [0x7f73da590bee]
 8: (ShardedThreadPool::shardedthreadpool_worker(unsigned int)+0x839) [0x7f73daaf9439]
 9: (ShardedThreadPool::WorkThreadSharded::entry()+0x10) [0x7f73daafb3d0]
 10: (()+0x7e25) [0x7f73d78c6e25]
 11: (clone()+0x6d) [0x7f73d69b935d]

log file (too big to upload here) see: http://imgs-1252230511.cossh.myqcloud.com/ceph.DATASTOR_B-osd.2.log


Files

1.png (62.2 KB) 1.png Chang Liu, 09/06/2018 09:53 AM
Actions #1

Updated by Josh Durgin over 5 years ago

  • Priority changed from Normal to High
Actions #2

Updated by Neha Ojha over 5 years ago

  • Status changed from New to Need More Info

Hi Chang. Can you reproduce this bug with higher level of debugging? It is hard to find out what's happening from these logs.

Actions #3

Updated by Chang Liu over 5 years ago

Neha Ojha wrote:

Hi Chang. Can you reproduce this bug with higher level of debugging? It is hard to find out what's happening from these logs.

Sorry Neha. I could not reproduce this bug. is it related to ERROR PGLog?

Actions #4

Updated by Josh Durgin over 5 years ago

It may be related to error-pg-log entry bugs in 12.2.2. The latest luminous releases have fixed a few of these.

Actions #5

Updated by Josh Durgin over 4 years ago

  • Status changed from Need More Info to Can't reproduce
Actions

Also available in: Atom PDF