Quoting Sage Weil (2013-06-11 11:43:30) > I'm also seeing this hang regularly with both 3.9 and 3.10-rc5. Is this > is a known problem? In this case there is no powercycling; just a regular > ceph-osd workload. Everyone here is waiting for the root node, but it isn't immediately clear who has the lock. log_one_extent is the most likely suspect, but I can't see how it would be scheduling with the root lock held. Could you please sysrq-w? -chris -- 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
