From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>,
Boaz Harrosh <bharrosh@panasas.com>
Subject: Re: unlink within an open directory stream
Date: Sat, 24 Mar 2012 12:53:47 -0400 (EDT) [thread overview]
Message-ID: <275611967.8.1332608027370.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <1332607503.25346.2.camel@lade.trondhjem.org>
Hi,
I don't think anything is. Or, people originally reported the behavior against knfsd.
Matt
----- "Trond Myklebust" <Trond.Myklebust@netapp.com> wrote:
> On Sat, 2012-03-24 at 12:34 -0400, Matt W. Benjamin wrote:
> > Hi,
> >
> > Folks testing linux nfs + Ganesha with bonnie++ have noticed the
> issue described here (but I didn't see traffic on this list):
> >
> > http://bugs.centos.org/view.php?id=5496
> > https://bugzilla.redhat.com/show_bug.cgi?id=789452
> >
> > Ie, an application which unlinks on an open (nfs) directory stream,
> and continues to read and unlink progressively, will generally not see
> all the entries originally in the stream. Reopening the stream ives
> the "correct" result. So, apparently older clients were more
> forgiving, as mentioned in the links. Is the current behavior one the
> client is intending?
> >
> > Thanks,
> >
> > Matt
>
> What is so particular about the ganesha readdir implementation?
>
> --
> Trond Myklebust
> Linux NFS client maintainer
>
> NetApp
> Trond.Myklebust@netapp.com
> www.netapp.com
--
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104
http://linuxbox.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
next prev parent reply other threads:[~2012-03-24 16:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <209745840.4.1332606289405.JavaMail.root@thunderbeast.private.linuxbox.com>
2012-03-24 16:34 ` unlink within an open directory stream Matt W. Benjamin
2012-03-24 16:44 ` Myklebust, Trond
2012-03-24 16:53 ` Matt W. Benjamin [this message]
2012-03-24 17:12 ` Myklebust, Trond
2012-03-24 17:43 ` Matt W. Benjamin
2012-03-26 18:17 ` Boaz Harrosh
2012-03-26 18:25 ` Myklebust, Trond
2012-03-26 18:43 ` Boaz Harrosh
2012-03-26 18:55 ` Matt W. Benjamin
2012-03-26 19:01 ` Myklebust, Trond
2012-03-26 19:07 ` Boaz Harrosh
2012-03-30 15:24 ` Peter Staubach
2012-03-30 15:46 ` Myklebust, Trond
2012-03-30 16:46 ` Peter Staubach
2012-03-30 17:10 ` Matt W. Benjamin
2012-03-30 20:17 ` Jeff Layton
2012-04-04 15:35 ` Jeff Layton
2012-04-05 8:45 ` Benny Halevy
[not found] <1598378492.82.1332790088063.JavaMail.root@thunderbeast.private.linuxbox.com>
2012-03-26 19:29 ` Matt W. Benjamin
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=275611967.8.1332608027370.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@linuxbox.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bharrosh@panasas.com \
--cc=linux-nfs@vger.kernel.org \
/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.