From: Christoph Hellwig <hch@infradead.org>
To: Mike Krieger <mikeyk@instagram.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS / xfssyncd lock-ups on 2.6.38-8
Date: Sun, 20 Nov 2011 13:32:23 -0500 [thread overview]
Message-ID: <20111120183223.GA19572@infradead.org> (raw)
In-Reply-To: <A734D23E-8544-4261-A699-90B689887F46@instagram.com>
On Sun, Nov 20, 2011 at 08:34:02AM -0800, Mike Krieger wrote:
> Would appreciate any thoughts/pointers to fixes or workarounds if this is a known issue.
This was fixed by:
xfs: force the log if we encounter pinned buffers in .iop_pushbuf
in Linux 3.1. I've also backported it to the 3.0-stable issues. I
would recommend to upgrade to the latest Linux 3.0-stable release, as
I'll plan to backport all important XFS fixes to it.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-20 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-20 16:34 XFS / xfssyncd lock-ups on 2.6.38-8 Mike Krieger
2011-11-20 18:32 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-13 11:44 Haefliger, Juerg
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=20111120183223.GA19572@infradead.org \
--to=hch@infradead.org \
--cc=mikeyk@instagram.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