On Sat, Nov 26, 2011 at 03:14:37PM +0100, Stefan Kleijkers wrote: > 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. >
Well those look perfect, but that shouldn't be happening, essentially what that tells me is we've somehow thought that we already have space reserved for that inode, but we don't, and the only way we test/set that value is under a spin_lock, so it simply cannot be happening that way. So can you jack up your buffer size for ftrace and re-run and get me the same info again to make sure nothing to lost? You can do that by doing something like this echo 4096 > /sys/kernel/debug/traceing/buffer_size_kb and then running the test and gather the same info as before. Thanks, Josef -- 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
