On Thu, Apr 9, 2009 at 1:59 PM, Ying Han <yinghan@xxxxxxxxxx> wrote: > On Thu, Apr 9, 2009 at 1:30 PM, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: >> On Mon, 6 Apr 2009 12:23:29 +0200 >> Jan Kara <jack@xxxxxxx> wrote: >> >>> > >>> > I tried this patch and seems i got deadlock on the truncate_mutex. >>> > Here is the message after enabling lockdep. I pasted the same message >>> > on the origianal thread. >>> >>> ... >>> >>> I don't think this is a deadlock (or is the machine hung?). The thread >>> was just waiting for a long time. I'd think that you'll occasionally get >>> exactly the same message even without my patch if you stress the machine >>> like you do. >>> >> >> Well, it's easy to tell the difference >> >> deadlock: system never recovers >> long-sucky-delay: system eventually recovers. >> >> Which was it?? > Guess i have to retest it. I didn't wait long enough to see what > happened on the machine. However, i do see the machine got rebooted > later, but i am not sure what is the reason it is got reboot. > > I will rerun the patch and keep an eye on it this time. Ok, i rerun the patch and i don't see the message poping this time and the machine is up healthy. > > --Ying >> > -- 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
