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 23:51:50 +0200 [thread overview]
Message-ID: <413F7EF6.9050005@bluewin.ch> (raw)
In-Reply-To: <1094676419.8363.42.camel@lade.trondhjem.org>
> Unless you have allocated a large buffer for it, readdir() will end up
> calling multiple times down into the kernel, so the read of an entire
> directory is NOT going to be atomic.
> If the mtime on the directory has changed in the meantime, the cached
> version may be flushed out, and the directory read in again. If the
> server has screwed up the cookies, then that will confuse the client.
OK, right. I tracked down one incident captured here:
http://www.nies.ch/download/apple-nfs-loop-1dir.dump.gz
A READDIRPLUS reports a directory entry "." with cookie 276 (Frame 157)
and the next READDIRPLUS reports a file "package-use.html" with same
cookie 276 (Frame 161). This is WRONG by the server, right?
But why is it working then without problems on a Solaris NFS client?
Well, seems that I have to call Apple support and listen to one hour
iTunes again ...
Thanks a lot.
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 21:52 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
2004-09-08 20:46 ` Trond Myklebust
2004-09-08 21:51 ` Bernd Nies [this message]
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=413F7EF6.9050005@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.