From: Dave Chinner <david@fromorbit.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Christoph Hellwig <hch@infradead.org>,
Greg KH <gregkh@linuxfoundation.org>,
Philipp Herz - Profihost AG <p.herz@profihost.ag>,
stable@vger.kernel.org, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS blocked task in xlog_cil_force_lsn
Date: Tue, 17 Apr 2012 09:56:47 +1000 [thread overview]
Message-ID: <20120416235647.GA6734@dastard> (raw)
In-Reply-To: <4F8BC0B9.90604@profihost.ag>
On Mon, Apr 16, 2012 at 08:48:25AM +0200, Stefan Priebe - Profihost AG wrote:
> Hi,
>
> today i've seen this call trace / block in XFS while running 3.0.27.
>
> INFO: task xfsaild/sdc3:1818 blocked for more than 120 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> xfsaild/sdc3 D ffff88041f374dc8 0 1818 2 0x00000000
> ffff88041edd3d30 0000000000000046 ffff8803ecaa8dc0 ffff88041f23fe28
> ffff88041f374860 0000000000010800 ffff88041edd3fd8 ffff88041edd2010
> ffff88041edd3fd8 0000000000010800 ffff88041f15c860 ffff88041f374860
> Call Trace:
> [<ffffffff8159c94a>] schedule+0x3a/0x60
> [<ffffffff812763a9>] xlog_cil_force_lsn+0xe9/0x110
> [<ffffffff8104caf0>] ? try_to_wake_up+0x2a0/0x2a0
> [<ffffffff81273922>] _xfs_log_force+0x62/0x250
> [<ffffffff81273d23>] xfs_log_force+0x13/0x40
> [<ffffffff81281ac7>] ? xfs_trans_ail_cursor_next+0x27/0x30
> [<ffffffff81282237>] xfsaild+0x447/0x460
> [<ffffffff81281df0>] ? xfs_trans_ail_init+0xb0/0xb0
> [<ffffffff8106f646>] kthread+0x96/0xa0
> [<ffffffff815a0214>] kernel_thread_helper+0x4/0x10
> [<ffffffff8106f5b0>] ? kthread_worker_fn+0x130/0x130
> [<ffffffff815a0210>] ? gs_change+0xb/0xb
>
> Is there a known fix / patch available?
Your first question should be: is this a known problem?
And the answer to that is: I don't think so.
So, is the system actually hung? Were there IO errors around this
time? did the system recover and continue to work normally? What's
your storage hardware, application, workload, etc?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-04-16 23:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 6:48 XFS blocked task in xlog_cil_force_lsn Stefan Priebe - Profihost AG
2012-04-16 23:56 ` Dave Chinner [this message]
2012-04-17 8:19 ` Stefan Priebe - Profihost AG
2012-04-17 8:32 ` Dave Chinner
2012-04-17 9:19 ` Stefan Priebe - Profihost AG
-- strict thread matches above, loose matches on Subject: below --
2013-12-18 2:05 Kevin Richter
2013-12-18 3:38 ` Stan Hoeppner
2013-12-18 10:27 ` Kevin Richter
2013-12-19 14:11 ` Stan Hoeppner
2013-12-20 10:26 ` Kevin Richter
2013-12-20 12:36 ` Stan Hoeppner
2013-12-21 5:30 ` Dave Chinner
2013-12-22 9:18 ` Stan Hoeppner
2013-12-22 20:14 ` Dave Chinner
2013-12-22 21:01 ` Michael L. Semon
2013-12-22 2:35 ` Kevin Richter
2013-12-22 8:12 ` Stan Hoeppner
2013-12-22 14:10 ` Kevin Richter
2013-12-22 17:29 ` Stan Hoeppner
2013-12-20 22:43 ` Arkadiusz Miśkiewicz
2013-12-18 8:33 ` Stefan Ring
2013-12-18 22:21 ` Dave Chinner
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=20120416235647.GA6734@dastard \
--to=david@fromorbit.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=p.herz@profihost.ag \
--cc=s.priebe@profihost.ag \
--cc=stable@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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