On Monday 2013-01-14 09:50, Sedat Dilek wrote: >On Mon, Jan 14, 2013 at 1:10 AM, Jan Engelhardt <jengelh@xxxxxxx> wrote: >> >> I thought these were fixed, but I just got one on 3.7.1 on x86_64. >> >> [648141.344931] INFO: task sync:10395 blocked for more than 480 seconds. >> [648141.344969] [<ffffffff813ebc8b>] schedule_timeout+0x1c/0xf7 >> [648141.344975] [<ffffffff813ec714>] wait_for_common+0x9a/0x115 >> [648141.344982] [<ffffffff8112ee60>] sync_inodes_sb+0xaa/0x18c >> [648141.344988] [<ffffffff811125ee>] iterate_supers+0x63/0xb4 >> [648141.344993] [<ffffffff81131fdc>] sys_sync+0x2e/0x81 >> [648141.344999] [<ffffffff813f39ed>] system_call_fastpath+0x1a/0x1f >> [648141.345025] [<00007f85ffdef117>] 0x7f85ffdef116 >> >Can you test w/ Linux v3.7.2? > >Not sure but this sounds like a fix for your problem: >commit 9359dd031b11100a3532ef7bfc04f2fc7f23c33b >"mm: fix calculation of dirtyable memory" It seems to be resolved in 3.7.2 and subsequent releases, thank you. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
