Howdy all,

We've been plagued buy this ext3 bug since 2.6.10, and it only happens
on heavily loaded postgres systems.  We run our postgres DB on ext3
data=journal on a dmcrypt partition.  Our kernel is also patched with
grsec, but that doesn't appear to play any role.

After upgrading to 2.6.11.12 (specifically for the ext3 checkpoint.c
fix) we noticed two things.  The assertion failure persists, and now
we get a condition where a postgres process will spin in state 'D'
forever and hog 100% of a CPU (in system, not user).

I've attached the trace in plain text so the formatting doesn't get screwed.

Let me know if anyone would like more information.  I'm no programmer,
but I'd like to help in any way that I can.