[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200710192259.l9JMxaAT006804@agora.fsl.cs.sunysb.edu>
Date: Fri, 19 Oct 2007 18:59:36 -0400
From: Erez Zadok <ezk@...sunysb.edu>
To: Trond Myklebust <trond.myklebust@....uio.no>
Cc: Erez Zadok <ezk@...sunysb.edu>, bfields@...ldses.org,
nfs@...ts.sourceforge.net, neilb@...e.de,
linux-kernel@...r.kernel.org
Subject: Re: nfsv2 ref leak in 2.6.24?
In message <1192830752.7466.32.camel@...mdal.trondhjem.org>, Trond Myklebust writes:
>
> On Fri, 2007-10-19 at 17:40 -0400, Erez Zadok wrote:
[...]
> > Trond, I was able to narrow down the problem w/o using unionfs at all (yay!
> > :-). All I do is setup a loop device, mkfs it as ext2, mount it, then
> > export it to localhost and mount it locally as nfs2. I go and touch a new
> > file in the ext2 directory. Then I readdir the export point to find the new
> > file indeed. Then I stat(1) the new file, and get the appropriate stat
> > output. Now the strange thing is that right after the stat through the
> > export point, the file DISAPPEARS from the lower ext2 dir, but REAPPEARS a
> > few seconds later.
>
> Let me get this straight:
>
> 1) You create the file on the server
> 2) You readdir the file from the client
> 3) You stat the file from the client
>
> ....with the result that the file disappears from sight on the server?
Yup.
> That would indicate some dcache issues with the server code. What export
> options are you using?
The explicit command I use is:
exportfs -o no_root_squash,rw localhost:/n/export/b0
The options recorded in exportfs -v:
/n/export/b0 localhost.localdomain(rw,wdelay,no_root_squash,no_subtree_check,anonuid=65534,anongid=65534)
Erez.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists