2011/11/26 Stefan Kleijkers <ste...@unilogicnetworks.net>: > Hello Josef, > > I've new results, is this the trace you are looking for? > > Trace of OSD0: http://pastebin.com/gddLBXE4 > Dmesg of OSD0: http://pastebin.com/Uebzgkjv > > OSD1 crashed a while later with the same messages. > > Stefan
Hi Josef, I ran your patch on one of our ceph nodes, too. At the first run it hit the BUG_ON and creashed. Unfortunately I was not able to get the trace messages from the server (I'm glad that Stefan managed to fetch it), so I gave it a second spin. This time it did NOT hit the BUG_ON, but I wrote the trace to a file, so I can send you the trace output at that time. You can find dmesg-output here: http://pastebin.com/pWWsZ79e The trace messages from 154900 till 154999 are here (don't know if this is interesting): http://pastebin.com/01EKHqn5 and the tracing output from 206200 till 206399 is here: http://pastebin.com/50PNtiF7 I hope, that this will give you a better insight into this. I will now reboot and run it a third time, to see if I can hit the BUG_ON again. Regards, Christian -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
