From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: nfsv2 ref leak in 2.6.24?
Date: Fri, 19 Oct 2007 09:41:16 -0400
Message-ID: <1192801277.7073.4.camel@heimdal.trondhjem.org>
References: <200710190549.l9J5nnX8007119@agora.fsl.cs.sunysb.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: bfields@fieldses.org, neilb@suse.de, nfs@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
To: Erez Zadok <ezk@cs.sunysb.edu>
In-Reply-To: <200710190549.l9J5nnX8007119@agora.fsl.cs.sunysb.edu>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net


On Fri, 2007-10-19 at 01:49 -0400, Erez Zadok wrote:
> I'm testing unionfs on top of nfsv2/3/4, using 2.6.24 as of linus's commit
> 4fa4d23fa20de67df919030c1216295664866ad7.  A lot of my unionfs regression
> tests are failing on nfs2, b/c files that should be deleted, aren't.  It
> feels like there may be a ref leak that prevents the files from being
> deleted, or maybe an unlink issue.  It doesn't happen in all of my previous
> kernels w/ identical unionfs (code 2.6.9--2.6.23).  And in 2.6.24 it happens
> only w/ nfs2 -- nfs3/4 are fine.
> 
> I'm not sure if this is a client or server issue, and I'm only starting to
> dig deeper.  But I thought I'd ask you in case this is a known problem and
> you have a fix.  If this is the first you hear of this problem, let me know
> and I'll try to narrow it down further.

A couple of questions:

      * Are these files being sillyrenamed?
      * Are they shown as being removed by the server?

Cheers
  Trond


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs