linux-ext4 - Re: Ext4 flush blocked

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 15 Jul 2011 11:31:30 +0800
From:	Tao Ma <tm@....ma>
To:	Felipe Wilhelms Damasio - Taghos <felipewd@...hos.com.br>
CC:	Theodore Ts'o <tytso@....edu>, Andreas Dilger <adilger@....com>,
	linux-ext4@...r.kernel.org
Subject: Re: Ext4 flush blocked

Hi Felipe,
On 07/15/2011 09:27 AM, Felipe Wilhelms Damasio - Taghos wrote:
>     Hi Again,
> 
> Em 14/07/2011 22:19, Felipe Wilhelms Damasio - Taghos escreveu:
>>      After a while using (about an hour) I get a lot of:
>>
>> INFO: task flush-8:16:6650 blocked for more than 120 seconds.
> 
>     I also saw this:
> 
> INFO: task jbd2/sdb1-8:1672 blocked for more than 120 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> jbd2/sdb1-8   D 0000000000000004     0  1672      2 0x00000000
>  ffff88042e171aa0 0000000000000046 0000000000012500 ffff88042e171fd8
>  ffff88042e171fd8 ffff88042c2eadf0 0000000000012500 0000000000012500
>  0000000000012500 ffff88042c2eadf0 ffff88042e0d0690 ffff88042c2eb098
> Call Trace:
>  [<ffffffff8151c837>] io_schedule+0x7b/0xc2
>  [<ffffffff8108fceb>] sync_page+0x41/0x45
>  [<ffffffff8151cc1a>] __wait_on_bit+0x47/0x79
>  [<ffffffff8108fcaa>] ? sync_page+0x0/0x45
>  [<ffffffff8108fea1>] wait_on_page_bit+0x6e/0x75
>  [<ffffffff8104ed1c>] ? wake_bit_function+0x0/0x2a
>  [<ffffffff81097a36>] ? pagevec_lookup_tag+0x22/0x2b
>  [<ffffffff810965cb>] write_cache_pages+0x1d5/0x2e9
>  [<ffffffff81095ee0>] ? __writepage+0x0/0x2f
>  [<ffffffff810966fe>] generic_writepages+0x1f/0x25
>  [<ffffffff8114251d>] jbd2_journal_commit_transaction+0x35b/0x10b2
>  [<ffffffff81035288>] ? get_parent_ip+0x11/0x41
>  [<ffffffff811468bf>] kjournald2+0xd2/0x22b
>  [<ffffffff8104ece4>] ? autoremove_wake_function+0x0/0x38
>  [<ffffffff8151dbdf>] ? _raw_spin_unlock_irqrestore+0x2c/0x37
>  [<ffffffff811467ed>] ? kjournald2+0x0/0x22b
>  [<ffffffff8104e892>] kthread+0x7d/0x85
>  [<ffffffff810037d4>] kernel_thread_helper+0x4/0x10
>  [<ffffffff8104e815>] ? kthread+0x0/0x85
>  [<ffffffff810037d0>] ? kernel_thread_helper+0x0/0x10
> 
> 
>     Don't know if this helps, though.
> 
>     Is there something I can try to fix this?
could you please try to change io scheduler to 'deadline'?
We have met with some similar warnings and changing to 'deadline' makes
ext4 happy.

Thanks
Tao
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html