From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: linux-nfs@vger.kernel.org, Olga Kornievskaia <aglo@citi.umich.edu>
Subject: Re: gfs2/pnfs stall
Date: Wed, 12 May 2010 11:45:09 -0400 [thread overview]
Message-ID: <20100512154509.GA5226@fieldses.org> (raw)
In-Reply-To: <1273662210.2884.29.camel@localhost>
On Wed, May 12, 2010 at 12:03:30PM +0100, Steven Whitehouse wrote:
> Hi,
>
> On Tue, 2010-05-11 at 16:15 -0400, J. Bruce Fields wrote:
> > Olga ran across the following while running an iozone test (from the
> > Windows pnfs client) to a pnfs/gfs2 server built from 2.6.34-rc5-pnfs
> > commit 1ea22c6e65028535ecb62a4e00cf706fc6446b77.
> >
> > Any ideas?
> >
> It might well be the issue which we've been chasing down recently. Bob
> has proposed some patches which I've just pushed into the GFS2 -nmw tree
> this morning (and there is one that was pushed in a little while back
> too).
>
> We'd need a set of glock dumps to be certain, but it does look as if it
> might be that,
OK. Would it be useful for us to get you a glock dump or to test the
-nmw tree? (Looks like the latter is available from:
git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-nmw.git
. I didn't find instructions for the former....)
--b.
next prev parent reply other threads:[~2010-05-12 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 20:15 gfs2/pnfs stall J. Bruce Fields
2010-05-12 11:03 ` Steven Whitehouse
2010-05-12 15:45 ` J. Bruce Fields [this message]
2010-05-12 15:48 ` Steven Whitehouse
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=20100512154509.GA5226@fieldses.org \
--to=bfields@fieldses.org \
--cc=aglo@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=swhiteho@redhat.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;
as well as URLs for NNTP newsgroup(s).