On Nov 18, 2013, at 8:53 PM, Chris Murphy <li...@colorremedies.com> wrote:
> > On Nov 18, 2013, at 8:00 PM, Charles Cazabon > <charlesc-lists-bt...@pyropus.ca> wrote: >> >> This is on x86_64, server-class hardware (ECC memory, etc). I ran a scrub >> overnight that reported no errors, and I'll do it again now that I've >> reverted >> to 3.11.7. >> >> Is there any other info that might be useful to the btrfs devs about this? > > sysrq+w would dump the blockage to kernel messages. Depending on your kernel > you may need to first enable sysrq functions with > > echo 1 > /proc/sys/kernel/sysrq > > then > > echo 2 > /proc/sysrq-trigger Cute. That 2 is supposed to be a w, hence sysrq+w. Chris Murphy -- 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
