From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: bfields@fieldses.org, nfs@lists.sourceforge.net, neilb@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: nfsv2 ref leak in 2.6.24?
Date: Fri, 19 Oct 2007 09:41:16 -0400 [thread overview]
Message-ID: <1192801277.7073.4.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <200710190549.l9J5nnX8007119@agora.fsl.cs.sunysb.edu>
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
next prev parent reply other threads:[~2007-10-19 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 5:49 Erez Zadok
2007-10-19 13:41 ` Trond Myklebust [this message]
2007-10-19 21:40 ` Erez Zadok
2007-10-19 21:52 ` Trond Myklebust
2007-10-19 22:59 ` Erez Zadok
2007-10-20 2:33 ` Erez Zadok
2007-10-20 17:12 ` Trond Myklebust
2007-10-20 19:04 ` Erez Zadok
2007-10-20 21:35 ` Erez Zadok
2007-10-21 16:58 ` Trond Myklebust
2007-10-21 22:18 ` Erez Zadok
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=1192801277.7073.4.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=bfields@fieldses.org \
--cc=ezk@cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®