From: Christoph Hellwig <hch@infradead.org>
To: linux-nfs@vger.kernel.org
Subject: Re: xfstests generic/075 failure on recent Linus' tree
Date: Fri, 16 Jan 2015 05:39:05 -0800 [thread overview]
Message-ID: <20150116133905.GA473@infradead.org> (raw)
In-Reply-To: <20141020173658.GA7552@infradead.org>
FYI, I'm still seeing this in current Linus' HEAD, not just on
a single machine, but also when using multiple VMs on the same host.
I can't actually test multiple physical hosts, so I wonder if anyone
else can still reproduce it, and if yes wit which setup.
On Mon, Oct 20, 2014 at 10:36:58AM -0700, Christoph Hellwig wrote:
> Running 4.1 against a same host server backed off XFS I run into
> a hang in generic/075:
>
> generic/075 18s ...[ 408.796877] nfs: server 127.0.0.1 not responding, still trying
> [ 408.799131] nfs: server 127.0.0.1 not responding, still trying
> [ 408.801357] nfs: server 127.0.0.1 not responding, still trying
> [ 443.676971] nfs: server 127.0.0.1 not responding, timed out
> [ 623.837009] nfs: server 127.0.0.1 not responding, timed out
> [ 628.716855] nfs: server 127.0.0.1 not responding, timed out
> [ 803.996883] nfs: server 127.0.0.1 not responding, timed out
> [ 813.783542] nfs: server 127.0.0.1 not responding, timed out
> [ 984.156873] nfs: server 127.0.0.1 not responding, timed out
> [ 998.876901] nfs: server 127.0.0.1 not responding, timed out
>
---end quoted text---
prev parent reply other threads:[~2015-01-16 13:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 17:36 xfstests generic/075 failure on recent Linus' tree Christoph Hellwig
2014-10-21 13:12 ` Boaz Harrosh
2014-10-22 11:46 ` Christoph Hellwig
2014-10-22 12:00 ` Trond Myklebust
2014-10-22 13:08 ` Christoph Hellwig
2014-10-24 8:14 ` Trond Myklebust
2014-10-24 10:08 ` [PATCH] nfsd: Ensure that NFSv4 always drops the connection when dropping a request Trond Myklebust
2014-10-24 11:26 ` Jeff Layton
2014-10-24 13:34 ` Jeff Layton
2014-10-24 14:30 ` Trond Myklebust
2014-10-24 14:57 ` Jeff Layton
2014-10-24 15:59 ` Trond Myklebust
2014-10-24 17:08 ` Jeff Layton
2014-10-27 19:00 ` Jeff Layton
2014-10-24 13:42 ` Christoph Hellwig
2015-01-16 13:39 ` Christoph Hellwig [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=20150116133905.GA473@infradead.org \
--to=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.