From: Bernd Nies <bnies@bluewin.ch>
To: nfs@lists.sourceforge.net
Subject: Re: ls hangs on NFS share from Apple Xserve
Date: Wed, 08 Sep 2004 22:07:41 +0200 [thread overview]
Message-ID: <413F668D.4060601@bluewin.ch> (raw)
In-Reply-To: <1094673208.8363.21.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> As far as I can see from your traces, 2 consecutive READDIRs on the same
> directory is giving totally different results...
>
> In your TCP file, the first time the Linux client reads through the
> directory which begins with "Autorun.inf", the entry "install.sh" (for
> instance) has cookie 292. The second time round, it has cookie 252.
>
> Our client will not work with such a server.
Are you sure it reads the same directory twice? A ls -lR shouldn't do
this and I ran it only once per traffic capture. Between the UDP and NFS
traffics I unmounted the directory. The share contains directories which
contents are sometimes similar.
The server is working fine. Only on about one of thousand directories
the client loops and if Client A loops over one directory, client B does
not.
Regards,
Bernd
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-09-08 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 8:42 ls hangs on NFS share from Apple Xserve bnies
2004-09-08 16:52 ` Trond Myklebust
2004-09-08 18:36 ` Bernd Nies
2004-09-08 19:53 ` Trond Myklebust
2004-09-08 20:07 ` Bernd Nies [this message]
2004-09-08 20:46 ` Trond Myklebust
2004-09-08 21:51 ` Bernd Nies
2004-09-08 22:30 ` Trond Myklebust
2004-09-09 8:08 ` bnies
2004-09-09 15:00 ` Trond Myklebust
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=413F668D.4060601@bluewin.ch \
--to=bnies@bluewin.ch \
--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 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.