From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: connectathon test failures Date: Wed, 8 Oct 2008 22:10:11 -0400 Message-ID: <20081009021011.GB17896@fieldses.org> References: <20081008225543.GG14527@fieldses.org> <20081009020300.GA17896@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-nfs@vger.kernel.org To: Trond Myklebust Return-path: Received: from mail.fieldses.org ([66.93.2.214]:41083 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754995AbYJICKM (ORCPT ); Wed, 8 Oct 2008 22:10:12 -0400 In-Reply-To: <20081009020300.GA17896@fieldses.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Wed, Oct 08, 2008 at 10:03:00PM -0400, bfields wrote: > 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()". Err, sorry, no: that was the last *good* one! It's the following one ( (4dc05efb86 "NFS: Convert __nfs_revalidate_inode() to use nfs_refresh_inode()") where the failures start. --b.