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 18:32:10 +1000 [thread overview]
Message-ID: <20120417083210.GI6734@dastard> (raw)
In-Reply-To: <4F8D27A1.2090809@profihost.ag>
On Tue, Apr 17, 2012 at 10:19:45AM +0200, Stefan Priebe - Profihost AG wrote:
> Am 17.04.2012 01:56, schrieb Dave Chinner:
> > Your first question should be: is this a known problem?
> > And the answer to that is: I don't think so.
> Sorry absolutely correct.
>
> > So, is the system actually hung?
> No. The kernel has ended the stalled request.
>
> > Were there IO errors around this time?
> No.
>
> > did the system recover and continue to work normally?
> Yes.
>
> > What's your storage hardware, application, workload, etc?
> It a Raid 10 of 1TB SATA Drives in front of a 3Ware Controller doing
> heavy rsync backups.
Hmmm. It sounds like it is just taking a long time for the IO to
complete, not that there is any other problem. If the IO is realy,
really slow, the a log force is definitely a place it coul dstall
for some time.
Does the RAID controller have a BBWC? What IO scheduler are you
using? Does mounting with nobarriers reduce the stall time? Can you
reduce the IO load so that it doesn't end up in this state?
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-17 8:32 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
2012-04-17 8:19 ` Stefan Priebe - Profihost AG
2012-04-17 8:32 ` Dave Chinner [this message]
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=20120417083210.GI6734@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