> We will try to give it a shot. But it might be hard to reproduce. > This problem occurred only once, after one week of very heavy > (over)stress tests. Yeah, understood. > Is it at least possible to confirm, that this is definitely the BTRFS > problem? *Definitely*? No, sadly, the kernel is simply not robust enough to isolate problems to the subsytem that caused them :). It's likely that this is a bug in btrfs, yes. But it's always technically possible that some other part of the kernel corrupted memory and the btrfs spinlock was the innocent victim. - z -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
