Am Sonntag 10 Januar 2010 21:19:26 schrieb Chris Mason: > On Sun, Jan 10, 2010 at 09:05:46PM +0100, Johannes Hirte wrote: > > I've observed this hanging task now several times. Not sure when this > > started, but 2.6.32 is affected too, IIRC. I don't have a test pattern > > for this. Dovecot imap triggers this from time to time. I've enabled > > CONFIG_DETECT_HUNG_TASK now > > > and got this two tasks which hang: > You're stuck on a read, could you please do a sysrq-w when this happens? Will do so when it happens again. > Also, do you eventually recover or are you stuck forever? I didn't wait too long when it happened, so I'm not sure. The longest time I've waited was 20-30min, until reboot without recover. So either it's stuck forever or it takes really long to recover. And one question I have: How do you identify a read in this call trace? regards, Johannes -- 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
