Can you send the osd logs? The merge_log crashes are probably fixable if I can see the logs. The leveldb crash is almost certainly a result of memory corruption. Thanks -Sam On Mon, Jun 4, 2012 at 9:16 AM, Tommi Virtanen <tv@xxxxxxxxxxx> wrote: > On Mon, Jun 4, 2012 at 1:44 AM, Yann Dupont <Yann.Dupont@xxxxxxxxxxxxxx> wrote: >> Results : Worked like a charm during two days, apart btrfs warn messages >> then OSD begin to crash 1 after all 'domino style'. > > Sorry to hear that. Reading through your message, there seem to be > several problems; whether they are because of the same root cause, I > can't tell. > > Quick triage to benefit the other devs: > > #1: kernel crash, no details available >> 1 of the physical machine was in kernel oops state - Nothing was remote > > #2: leveldb corruption? may be memory corruption that started > elsewhere.. Sam, does this look like the leveldb issue you saw? >> [push] v 1438'9416 snapset=0=[]:[] snapc=0=[]) v6 currently started >> 0> 2012-06-03 12:55:33.088034 7ff1237f6700 -1 *** Caught signal >> (Aborted) ** > ... >> 13: (leveldb::InternalKeyComparator::FindShortestSeparator(std::string*, >> leveldb::Slice const&) const+0x4d) [0x6ef69d] >> 14: (leveldb::TableBuilder::Add(leveldb::Slice const&, leveldb::Slice >> const&)+0x9f) [0x6fdd9f] > > #3: PG::merge_log assertion while recovering from the above; Sam, any ideas? >> 0> 2012-06-03 13:36:48.147020 7f74f58b6700 -1 osd/PG.cc: In function >> 'void PG::merge_log(ObjectStore::Transaction&, pg_info_t&, pg_log_t&, int)' >> thread 7f74f58b6700 time 2012-06-03 13:36:48.100157 >> osd/PG.cc: 402: FAILED assert(log.head >= olog.tail && olog.head >= >> log.tail) > > #4: unknown btrfs warnings, there should an actual message above this > traceback; believed fixed in latest kernel >> Jun 2 23:40:03 chichibu.u14.univ-nantes.prive kernel: [200652.479278] >> [<ffffffffa026fca5>] ? btrfs_orphan_commit_root+0x105/0x110 [btrfs] >> Jun 2 23:40:03 chichibu.u14.univ-nantes.prive kernel: [200652.479328] >> [<ffffffffa026965a>] ? commit_fs_roots.isra.22+0xaa/0x170 [btrfs] >> Jun 2 23:40:03 chichibu.u14.univ-nantes.prive kernel: [200652.479379] >> [<ffffffffa02bc9a0>] ? btrfs_scrub_pause+0xf0/0x100 [btrfs] >> Jun 2 23:40:03 chichibu.u14.univ-nantes.prive kernel: [200652.479415] >> [<ffffffffa026a6f1>] ? btrfs_commit_transaction+0x521/0x9d0 [btrfs] >> Jun 2 23:40:03 chichibu.u14.univ-nantes.prive kernel: [200652.479460] >> [<ffffffff8105a9f0>] ? add_wait_queue+0x60/0x60 >> Jun 2 23:40:03 chichibu.u14.univ-nantes.prive kernel: [200652.479493] >> [<ffffffffa026aba0>] ? btrfs_commit_transaction+0x9d0/0x9d0 [btrfs] >> Jun 2 23:40:03 chichibu.u14.univ-nantes.prive kernel: [200652.479543] >> [<ffffffffa026abb1>] ? do_async_commit+0x11/0x20 [btrfs] >> Jun 2 23:40:03 chichibu.u14.univ-nantes.prive kernel: [200652.479572] > -- > 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 -- 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
