From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: connectathon test failures
Date: Wed, 8 Oct 2008 22:03:00 -0400 [thread overview]
Message-ID: <20081009020300.GA17896@fieldses.org> (raw)
In-Reply-To: <20081008225543.GG14527@fieldses.org>
On Wed, Oct 08, 2008 at 06:55:43PM -0400, bfields wrote:
> I'm getting connectathon test failures with the latest merge of code
> from both our trees, linux-to-linux over v3 and v4.
>
> I just got this a moment ago, so haven't tried to track it down at all
> yet--but I seem to recall in the past this sort of failure has been an
> attribute revalidation problem (usually with the ext3 ctime resolution
> at least partly to blame).
The failure first happens with d65f557f3 "NFS: Fix
nfs_post_op_update_inode_force_wcc()".
--b.
next prev parent reply other threads:[~2008-10-09 2:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 22:55 connectathon test failures J. Bruce Fields
2008-10-09 2:03 ` J. Bruce Fields [this message]
2008-10-09 2:10 ` J. Bruce Fields
2008-10-09 14:36 ` Trond Myklebust
2008-10-09 15:53 ` J. Bruce Fields
2008-10-09 17:36 ` Trond Myklebust
2008-10-09 19:23 ` J. Bruce Fields
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=20081009020300.GA17896@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond@netapp.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 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.