Perhaps using gtest-style asserts (ASSERT_EQ(r, 0)) in Ceph would be useful so we can see parameter values to the assertion in the log. In this case, the return value from pthread_mutex_lock is almost certainly EINVAL, but it'd be informative to know for sure. On Tue, Feb 25, 2014 at 7:58 AM, Filippos Giannakos <philipgian@xxxxxxxx> wrote: > Hi Greg, > > Unfortunately we don't keep any Ceph related logs on the client side. On the > server side, we kept the default log settings to avoid overlogging. > Do you think that there might be something usefull on the OSD side ? > > On Tue, Feb 25, 2014 at 07:28:30AM -0800, Gregory Farnum wrote: >> Do you have logs? The assert indicates that the messenger got back >> something other than "okay" when trying to grab a local Mutex, which >> shouldn't be able to happen. It may be that some error-handling path >> didn't drop it (within the same thread that later tried to grab it >> again), but we'll need more details to track it down. >> -Greg >> Software Engineer #42 @ http://inktank.com | http://ceph.com >> > > Kind Regards, > -- > Filippos > <philipgian@xxxxxxxx> > -- > 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
