From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751784Ab1HTHD6 (ORCPT ); Sat, 20 Aug 2011 03:03:58 -0400 Received: from mailout.selfhost.de ([82.98.82.25]:55296 "EHLO outgoing.selfhost.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751153Ab1HTHD4 (ORCPT ); Sat, 20 Aug 2011 03:03:56 -0400 X-Greylist: delayed 400 seconds by postgrey-1.27 at vger.kernel.org; Sat, 20 Aug 2011 03:03:56 EDT Message-ID: <4E4F5AC8.3060302@afaics.de> Date: Sat, 20 Aug 2011 08:57:12 +0200 From: Harald Dunkel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: Kernel Mailing List Subject: filesystem access vs 120 seconds timeouts X-Enigmail-Version: 1.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks, on huge disk IO operations I get something like this from time to time: [ 6220.508495] INFO: task jbd2/sdb3-8:1616 blocked for more than 120 seconds. [ 6220.540831] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 6220.573046] jbd2/sdb3-8 D 0000000000000000 0 1616 2 0x00000000 [ 6220.573053] ffff88021216e050 0000000000000046 ffff8801eab35a40 0000000000000000 [ 6220.573058] ffffffff81401020 ffff8802121bbfd8 0000000000010300 0000000000004000 [ 6220.573063] ffff8802106cbac0 ffff8802106cba70 ffff88020ec1c000 ffffffff81136cc1 [ 6220.573069] Call Trace: [ 6220.573078] [] ? cfq_add_rq_rb+0xb6/0xc7 [ 6220.573085] [] ? kobject_get+0x12/0x17 [ 6220.573093] [] ? scsi_request_fn+0x374/0x44f [ 6220.573100] [] ? find_get_page+0x4a/0x76 [ 6220.573105] [] ? __lock_page+0x66/0x66 [ 6220.573111] [] ? io_schedule+0x4b/0x5d [ 6220.573116] [] ? sleep_on_page+0x6/0xa [ 6220.573121] [] ? __wait_on_bit+0x3e/0x71 [ 6220.573127] [] ? wait_on_page_bit+0x6e/0x73 [ 6220.573133] [] ? autoremove_wake_function+0x2a/0x2a [ 6220.573138] [] ? filemap_fdatawait_range+0x73/0x121 [ 6220.573155] [] ? submit_bio+0xb3/0xbc [ 6220.573166] [] ? jbd2_journal_commit_transaction+0x75f/0xf84 [jbd2] [ 6220.573170] [] ? lock_timer_base.isra.25+0x22/0x47 [ 6220.573174] [] ? kjournald2+0xc0/0x20a [jbd2] [ 6220.573177] [] ? abort_exclusive_wait+0x79/0x79 [ 6220.573181] [] ? commit_timeout+0x5/0x5 [jbd2] [ 6220.573184] [] ? kthread+0x76/0x7e [ 6220.573187] [] ? kernel_thread_helper+0x4/0x10 [ 6220.573190] [] ? kthread_worker_fn+0x139/0x139 [ 6220.573192] [] ? gs_change+0xb/0xb Is the timeout of 120 seconds still reasonable? Should I simply switch off the message, as suggested? Regards Harri -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk5PWsgACgkQUTlbRTxpHjdaKwCgkt5q3KABhq7FqNzit57A0eaP VQUAn0ChNyaIoSMOKmUK3dOtLjAQiAFj =H1Df -----END PGP SIGNATURE-----