Ted Ts'o, on 08/06/2010 10:10 PM wrote:
On Fri, Aug 06, 2010 at 05:23:46PM +0400, Vladislav Bolkhovitin wrote:
1. A bunch of detected hung tasks with call traces.
Do you eventually get file
system I/O errors that abort the journal transaction? You should...
Yes, as you can see in the previously attached log.
OK, so what are you complaining about? This is *normal*. You can
change how long the kernel will wait before printing the warnings, by
adjusting /proc/sys/kernel/hung_task_timeout_secs, but the fact that
you're getting the detected hung tasks is the system performing as
designed.
Well, I'm not complaining, I'm reporting.
I can't say where is the problem. And I really would *not* say that
activation of the hung tasks detector is normal. A correct timeout
should be set by default, not after manual user intervention.
2. "JBD: recovery failed" I reported before.
I've searched my mail archives, and I'm not sure what you're talking
about here. Maybe this was in an e-mail that you sent that perhaps
got lost?
It's next to the message on which you originally replied. It was
about ext3, but this time I saw it with ext4.
Can you resend, and with a new and specific subject line that is
helpful for finding it, and just that one message?
See http://lkml.org/lkml/2010/7/29/222 and
http://lkml.org/lkml/2010/7/29/325.
Vlad
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
