From: Andrew Morton <akpm@linux-foundation.org>
To: "Greg Donald" <gdonald@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: INFO: task reiserfs/0:1322 blocked for more than 120 seconds
Date: Tue, 19 Aug 2008 23:52:58 -0700 [thread overview]
Message-ID: <20080819235258.fa775505.akpm@linux-foundation.org> (raw)
In-Reply-To: <15e66e4e0808162136r2a439ee9wbb20f2b1f8fabc77@mail.gmail.com>
On Sat, 16 Aug 2008 23:36:03 -0500 "Greg Donald" <gdonald@gmail.com> wrote:
> I got this while rsync'ng an NFS share onto a local disk:
>
> [42374.151062] INFO: task reiserfs/0:1322 blocked for more than 120 seconds.
> [42374.186295] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> disables this message.
> [42374.229433] reiserfs/0 D c1f36180 0 1322 2
> [42374.265246] f5dbdedc 00000046 c1f36180 c1f36180 f5e932c0
> 1c823428 00002669 f5e932c0
> [42374.273706] f5e93514 c1f36180 00000000 f5dbc000 f62cc780
> f5e932c0 00000002 00000001
> [42374.313709] 00000000 00000000 f5e932c0 c013cc01 00000246
> f5dbded4 c013cbce e31e12ec
> [42374.356837] Call Trace:
> [42374.417842] [<c013cc01>] ? trace_hardirqs_on+0xb/0xd
> [42374.451201] [<c013cbce>] ? trace_hardirqs_on_caller+0xe9/0x111
> [42374.489735] [<c02e876b>] mutex_lock_nested+0x14b/0x22b
> [42374.525760] [<c01c9727>] ? flush_commit_list+0x119/0x505
> [42374.560839] [<c01c9727>] flush_commit_list+0x119/0x505
> [42374.594183] [<c01cca8e>] flush_async_commits+0x41/0x4b
> [42374.629770] [<c012ec1a>] run_workqueue+0xc3/0x18e
> [42374.662893] [<c012ebfe>] ? run_workqueue+0xa7/0x18e
> [42374.697814] [<c01cca4d>] ? flush_async_commits+0x0/0x4b
> [42374.732504] [<c012f609>] ? worker_thread+0x0/0x8a
> [42374.765765] [<c012f688>] worker_thread+0x7f/0x8a
> [42374.797749] [<c0131d61>] ? autoremove_wake_function+0x0/0x38
> [42374.833713] [<c0131c93>] kthread+0x40/0x69
> [42374.865772] [<c0131c53>] ? kthread+0x0/0x69
> [42374.897774] [<c010392f>] kernel_thread_helper+0x7/0x10
> [42374.929777] =======================
> [42374.957001] 3 locks held by reiserfs/0/1322:
> [42374.990140] #0: (reiserfs){--..}, at: [<c012ebe1>] run_workqueue+0x8a/0x18e
> [42375.025754] #1: (&(&journal->j_work)->work){--..}, at:
> [<c012ebfe>] run_workqueue+0xa7/0x18e
> [42375.062963] #2: (&jl->j_commit_mutex){--..}, at: [<c01c9727>]
> flush_commit_list+0x119/0x505
>
>
> I deleted a few GBs of data and ran it again but was unable to
> reproduce it. This was on 2.6.27-rc3.
>
> I don't see any corruption. Fluke?
>
Seems that about 100% of the reports we get of this warning triggering
are sys_sync, transaction commit, etc.
Does kerneloops.org disagree with me?
If not, I vote we kill it.
next prev parent reply other threads:[~2008-08-20 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-17 4:36 INFO: task reiserfs/0:1322 blocked for more than 120 seconds Greg Donald
2008-08-20 6:52 ` Andrew Morton [this message]
2008-08-20 9:19 ` Ingo Molnar
2008-08-20 10:00 ` Andi Kleen
2008-08-20 9:59 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080819235258.fa775505.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=gdonald@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox