From: Dave Chinner <david@fromorbit.com>
To: Peter Watkins <treestem@gmail.com>
Cc: Juerg Haefliger <juergh@gmail.com>, bpm@sgi.com, xfs@oss.sgi.com
Subject: Re: Still seeing hangs in xlog_grant_log_space
Date: Wed, 6 Jun 2012 09:54:47 +1000 [thread overview]
Message-ID: <20120605235447.GF22848@dastard> (raw)
In-Reply-To: <CAH4wwdFu7DEkHFZ5Bf7_PtLPsG0hUyUDoov03q=82R6t+QkERg@mail.gmail.com>
On Fri, May 25, 2012 at 01:03:04PM -0400, Peter Watkins wrote:
> On Fri, May 25, 2012 at 2:28 AM, Juerg Haefliger <juergh@gmail.com> wrote:
> >> Does your kernel have the effect of
> >>
> >> 0bf6a5bd4b55b466964ead6fa566d8f346a828ee xfs: convert the xfsaild
> >> thread to a workqueue
> >
> > No.
> >
> >
> >> c7eead1e118fb7e34ee8f5063c3c090c054c3820 xfs: revert to using a
> >> kthread for AIL pushing
> >
> > No.
> >
> >
> >> In particular, is this code in xfs_trans_ail_push:
> >>
> >> smp_wmb();
> >> xfs_trans_ail_copy_lsn(ailp, &ailp->xa_target, &threshold_lsn);
> >> smp_wmb();
> >
> > No. xfs_trans_ail_push looks like this:
> >
> > void
> > xfs_trans_ail_push(
> > struct xfs_ail *ailp,
> > xfs_lsn_t threshold_lsn)
> > {
> > xfs_log_item_t *lip;
> >
> > lip = xfs_ail_min(ailp);
> > if (lip && !XFS_FORCED_SHUTDOWN(ailp->xa_mount)) {
> > if (XFS_LSN_CMP(threshold_lsn, ailp->xa_target) > 0)
> > xfsaild_wakeup(ailp, threshold_lsn);
> > }
> > }
> >
> >
> > FWIW, the XFS driver in my kernel is identical to the vanilla 2.6.38
> > driver. I'm still trying to get a XFS trace from a production hang. I
> > do have a crash dump from a production machine with /tmp hanging.
> > Would it be helpful to share that dump?
> >
> > ...Juerg
>
> It looks like the combined effect of those patches, perhaps the write
> barriers, fix one log space hang. That problem exists in 2.6.38.
There are a huge number of fixes to solve these problems since
2.6.38. It doesn't help us at all to test anymore on 2.6.38,
especially as that kernel is not supported, and I'd suggest that you
migrate production off it sooner rather than later.
> Reading bug #922 I see your test case reproduces in recent kernels, so
> there must be a newer problem also.
Right, that's what we need to find - it appears to be a CIL
stall/accounting leak, completely unrelated to all the other AIL/log
space stalls that have been occurring. Last thing is that I was
waiting for more information on the stall that mark T @ sgi was able
to reproduce. I haven't heard anything from him since I asked for
more information on May 23....
> I find the reproducer the most useful, so no need to upload the dump.
At this point, running on a 3.5-rc1 kernel is what we need to get
working reliably. Once we have the problems solved there, we can
work out what set of patches need to be backported to 3.0-stable and
other kernels to fix the problems in those supported kernels...
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-06-05 23:54 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 12:09 Still seeing hangs in xlog_grant_log_space Juerg Haefliger
2012-04-23 14:38 ` Dave Chinner
2012-04-23 15:33 ` Juerg Haefliger
2012-04-23 23:58 ` Dave Chinner
2012-04-24 8:55 ` Juerg Haefliger
2012-04-24 12:07 ` Dave Chinner
2012-04-24 18:26 ` Juerg Haefliger
2012-04-25 22:38 ` Dave Chinner
2012-04-26 12:37 ` Juerg Haefliger
2012-04-26 22:44 ` Dave Chinner
2012-04-26 23:00 ` Juerg Haefliger
2012-04-26 23:07 ` Dave Chinner
2012-04-27 9:04 ` Juerg Haefliger
2012-04-27 11:09 ` Dave Chinner
2012-04-27 13:07 ` Juerg Haefliger
2012-05-05 7:44 ` Juerg Haefliger
2012-05-07 17:19 ` Ben Myers
2012-05-09 7:54 ` Juerg Haefliger
2012-05-10 16:11 ` Chris J Arges
2012-05-10 21:53 ` Mark Tinguely
2012-05-16 18:42 ` Ben Myers
2012-05-16 19:03 ` Chris J Arges
2012-05-16 21:29 ` Mark Tinguely
2012-05-18 10:10 ` Dave Chinner
2012-05-18 14:42 ` Mark Tinguely
2012-05-22 22:59 ` Dave Chinner
2012-06-06 15:00 ` Chris J Arges
2012-06-07 0:49 ` Dave Chinner
2012-05-17 20:55 ` Chris J Arges
2012-05-18 16:53 ` Chris J Arges
2012-05-18 17:19 ` Ben Myers
2012-05-19 7:28 ` Juerg Haefliger
2012-05-21 17:11 ` Ben Myers
2012-05-24 5:45 ` Juerg Haefliger
2012-05-24 14:23 ` Ben Myers
2012-05-07 22:59 ` Dave Chinner
2012-05-09 7:35 ` Dave Chinner
2012-05-09 21:07 ` Mark Tinguely
2012-05-10 2:10 ` Mark Tinguely
2012-05-18 9:37 ` Dave Chinner
2012-05-18 9:31 ` Dave Chinner
2012-05-24 20:18 ` Peter Watkins
2012-05-25 6:28 ` Juerg Haefliger
2012-05-25 17:03 ` Peter Watkins
2012-06-05 23:54 ` Dave Chinner [this message]
2012-06-06 13:40 ` Brian Foster
2012-06-06 17:41 ` Mark Tinguely
2012-06-11 20:42 ` Chris J Arges
2012-06-11 23:53 ` Dave Chinner
2012-06-12 13:28 ` Chris J Arges
2012-06-06 22:03 ` Mark Tinguely
2012-06-06 23:04 ` Brian Foster
2012-06-07 1:35 ` Dave Chinner
2012-06-07 14:16 ` Brian Foster
2012-06-08 0:28 ` Dave Chinner
2012-06-08 17:09 ` Ben Myers
2012-06-11 20:59 ` Mark Tinguely
2012-06-05 15:21 ` Chris J Arges
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=20120605235447.GF22848@dastard \
--to=david@fromorbit.com \
--cc=bpm@sgi.com \
--cc=juergh@gmail.com \
--cc=treestem@gmail.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