On Mon, Jun 25, 2012 at 08:08:31AM -0600, Stefan Priebe - Profihost AG wrote: > Am 25.06.2012 15:08, schrieb Josef Bacik:> > > This isn't showing the guy who's actually trying to commit the > > transaction. Next time this happens can you do a sysrq+w and capture > > the output and post it here so we can see what everybody is doing? > Thanks, > > > > Josef > > No problem. > > Kernel trace: > http://pastebin.com/raw.php?i=puZkCRCn > > # sys rq w trigger: > # echo w > /proc/sysrq-trigger > http://pastebin.com/raw.php?i=AQA8xxCX Thats weird, sysrq+w should have a bunch of stacktraces but it's empty, so unless theres a bug theres nothing blocked. Is the box actually hung or is it just taking forever? Maybe try sysrq+w again to see if the one you pasted was just a fluke? Thanks, Josef -- 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
