From: Ben Myers <bpm@sgi.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: shutdown xfs_sync_worker before the log
Date: Tue, 29 May 2012 12:04:30 -0500 [thread overview]
Message-ID: <20120529170430.GC4721@sgi.com> (raw)
In-Reply-To: <4FC4ED13.6030904@redhat.com>
Hey Brian,
On Tue, May 29, 2012 at 11:36:51AM -0400, Brian Foster wrote:
> On 05/29/2012 11:07 AM, Ben Myers wrote:
> > On Fri, May 25, 2012 at 03:45:36PM -0500, Ben Myers wrote:
> >> On Thu, May 24, 2012 at 05:39:52PM -0500, Ben Myers wrote:
> >>> Anyway, I'll make some time to work on this tomorrow so I can test it
> >>> over the weekend.
> >>
> >> This is going to spin over the weekend. See what you think.
> >
> > I'm reasonably satisfied with the test results over the weekend. I did end
> > up hitting an unrelated assert:
>
> I started testing the xfsaild idle patch based against the xfs tree over the
> weekend (after testing successfully against Linus' tree for several days) and
> reproduced the xfs_sync_worker() hang that Mark alerted me to last week. I
> was considering doing a bisect in that tree since it doesn't occur in Linus'
> tree, but it sounds like I can pull this patch now and shouldn't expect to
> reproduce the sync_worker() hang either, correct? Thanks.
D'oh! The xfs_sync_worker hang that Mark mentioned last week is when the sync
worker blocks on log reservation for the dummy transaction used to cover the
log, which means that it will not be calling xfs_ail_push_all, which might have
the effect of loosening things up a bit.
This thread is about a crash due to the xfs_sync_worker racing with unmount. A
fix for this crash is in Linus' tree as of late last week. Here we're looking
into replacing the existing fix with something that is a bit cleaner. s_umount
is overkill for this situation, so now we're calling cancel_delayed_work_sync
to shutdown the sync_worker before shutting down the log in order to prevent
the crash.
Unfortunately this fix won't help you with the hang. If you're considering
bisecting this, I think that Juerg Haefliger has reproduced a/the log hang all
the way back to 2.6.38. Also Chris J Arges has reproduced one on 2.6.32.52.
See thread 'Still seeing hangs in xlog_grant_log_space'. The log hang is a
wily coyote. ;)
Regards,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-29 16:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 17:43 BUG in xlog_get_lowest_lsn Ben Myers
2012-05-14 20:34 ` [PATCH] xfs: use s_umount sema in xfs_sync_worker Ben Myers
2012-05-15 18:30 ` Mark Tinguely
2012-05-15 19:06 ` Ben Myers
2012-05-16 1:56 ` Dave Chinner
2012-05-16 17:04 ` Ben Myers
2012-05-17 7:16 ` Dave Chinner
2012-05-23 9:02 ` Dave Chinner
2012-05-23 16:45 ` Ben Myers
2012-05-24 22:39 ` Ben Myers
2012-05-25 20:45 ` [PATCH] xfs: shutdown xfs_sync_worker before the log Ben Myers
2012-05-29 15:07 ` Ben Myers
2012-05-29 15:36 ` Brian Foster
2012-05-29 17:04 ` Ben Myers [this message]
2012-05-29 17:54 ` Brian Foster
2012-05-31 16:23 ` Mark Tinguely
2012-06-06 4:26 ` Dave Chinner
2012-06-11 20:45 ` Ben Myers
2012-06-11 21:11 ` Mark Tinguely
2012-06-11 23:36 ` Dave Chinner
2012-06-14 17:13 ` Mark Tinguely
2012-06-14 23:56 ` Dave Chinner
2012-06-20 7:44 ` Christoph Hellwig
2012-06-20 7:36 ` Christoph Hellwig
2012-06-20 17:18 ` Ben Myers
2012-06-20 22:59 ` Dave Chinner
2012-06-21 7:12 ` Christoph Hellwig
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=20120529170430.GC4721@sgi.com \
--to=bpm@sgi.com \
--cc=bfoster@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