From: Dave Chinner <david@fromorbit.com>
To: Laurence Oberman <loberman@redhat.com>
Cc: Leonardo Menezes Vaz <lvaz@redhat.com>, xfs@oss.sgi.com
Subject: Re: Tasks blocked in xlog_grant_log_space
Date: Mon, 17 Feb 2014 09:28:11 +1100 [thread overview]
Message-ID: <20140216222811.GW13647@dastard> (raw)
In-Reply-To: <461400101.2501294.1392394773671.JavaMail.zimbra@redhat.com>
On Fri, Feb 14, 2014 at 11:19:33AM -0500, Laurence Oberman wrote:
> Hello
>
> I have a customer seeing multiple tasks blocked in xlog_grant_log_space
> This lands up hitting the hungtask timer for pdflush.
>
> I have seen on the list that this issue is still out there.
> I also don't see outstanding I/O requests on the XFS file system that experienced this block.
>
> The last hung_task timeout was on dm-9
> ffff81011c78c080 ffff81081a43bc00 xfs /dev/vgautocomp/lv_autocomp /bb/autocomp
>
> crash> gendisk ffff810814d24400 | grep in_flight
> in_flight = 0,
>
> So just wondering if I am hitting an existing bug or if its a new one.
>
> This is an older 2.6.18 kernel
There's been lots of problems fixed in this area in the past seven
years. Your best bet is to upgrade to a more recent 3.x based kernel
where the known issues in this area have been resolved.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-02-16 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <532438291.2495843.1392394364516.JavaMail.zimbra@redhat.com>
2014-02-14 16:19 ` Tasks blocked in xlog_grant_log_space Laurence Oberman
2014-02-16 22:28 ` Dave Chinner [this message]
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=20140216222811.GW13647@dastard \
--to=david@fromorbit.com \
--cc=loberman@redhat.com \
--cc=lvaz@redhat.com \
--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