On Thursday, May 31, 2012 at 7:43 AM, Noah Watkins wrote: > > On May 31, 2012, at 6:20 AM, Nam Dang wrote: > > > > Stack: [0x00007ff6aa828000,0x00007ff6aa929000], > > > sp=0x00007ff6aa9274f0, free space=1021k > > > Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) > > > C [libcephfs.so.1+0x139d39] Mutex::Lock(bool)+0x9 > > > > > > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > > > j com.ceph.fs.CephMount.native_ceph_mkdirs(JLjava/lang/String;I)I+0 > > > j com.ceph.fs.CephMount.mkdirs(Ljava/lang/String;I)V+6 > > > j Benchmark$CreateFileStats.executeOp(IILjava/lang/String;Lcom/ceph/fs/CephMount;)J+37 > > > j Benchmark$StatsDaemon.benchmarkOne()V+22 > > > j Benchmark$StatsDaemon.run()V+26 > > > v ~StubRoutines::call_stub > > > > > > Nevermind to my last comment. Hmm, I've seen this, but very rarely. Noah, do you have any leads on this? Do you think it's a bug in your Java code or in the C/++ libraries? Nam: it definitely shouldn't be segfaulting just because a monitor went down. :) -Greg -- 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
