On Wed, 5 Dec 2012, Stefan Priebe - Profihost AG wrote: > There was a dump in the attached log. The stack trace is there, but with 'debug journal = 0/20' in your conf it will also dump all of the journal logging activity leading up to that point. Can you reproduce with that enabled? That should tell me why op < commited_seq. Thanks! sage > > Stefan > > Am 05.12.2012 um 15:41 schrieb Sage Weil <sage@xxxxxxxxxxx>: > > > On Wed, 5 Dec 2012, Stefan Priebe - Profihost AG wrote: > >> Hello list, > >> > >> i updated to latest next from today and then after 20 minutes an OSD was > >> crashing in os/JournalingObjectStore.cc. > >> > >> Attached is the log. > > > > Hmm, this is perplexing. It might just be a bad assert, but I can't see > > how it could happen. Any chance you can reproduce with > > > > debug journal = 0/10 > > > > in the [osd] section? That will give us a dump if it fails the assert. > > > > Thanks! > > s > > -- > > 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 > > -- 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