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 20:36:23 +0200 [thread overview]
Message-ID: <413F5127.5030008@bluewin.ch> (raw)
In-Reply-To: <1094662327.9493.42.camel@lade.trondhjem.org>
Hi Trond,
>>Martin Algesten reported that this might be caused by non-unique NFS cookies
>>in the same READDIRPLUS reply from the Apple NFS server but in our environment
>>with MacOS X 10.3.5 and SuSE Linux 9.0 (Kernel 2.4.21-243-smp4G, glibc-2.3.2-88)
>>I cannot confirm this. The NFS cookies are unique in the same READDIRPLUS
>>reply but not unique during the same NFS session.
>>
>
>
> What does this mean? That 2 different READDIRPLUS entries for the same
> directory may return the same cookie? That would a server bug...
The problem reported by Martin Algesten was: His MacOS X 10.3.4 NFS
server sent a duplicate Cookie within the _same_ READDIRPLUS reply. See:
http://algesten.blogspot.com/index.html#109103599929132337
I can't observe that on our MacOS X 10.3.5 server. I only see that while
traversing a NFS share with ls -lR on a Linux client the same Cookie ID
appears in different READDIRPLUS replies of different directories.
Because our Solaris NFS servers do the same and Linux NFS client works
fine with it, I guess this is allowed.
So I think the endless looping ls -lR from a Linux NFS client on a Mac
OS X 10.3.5 NFS share I reported is not related to that bug reported by
Martin Algesten.
Here is the ethereal snoop of such an incident:
http://www.nies.ch/download/apple-linux-nfs-loop.tar.gz
I did a ls -lR on a MacOS X NFS share and in a certain directory it
hung. A strace on the ls process shows that it loops over these system
calls:
getdents64(5, /* 3 entries */, 4096) = 128
lstat64("/share/dir/file1.txt", {st_mode=S_IFREG|0444, st_size=8550,
...}) = 0
getxattr("/share/dir/file1.txt", "system.posix_acl_access", (nil), 0) =
-1 EOPNOTSUPP (Operation not supported)
lstat64("/share/dir/file2.txt", {st_mode=S_IFREG|0444, st_size=6570,
...}) = 0
getxattr("/share/dir/file2.txt", "system.posix_acl_access", (nil), 0) =
-1 EOPNOTSUPP (Operation not supported)
lstat64("/share/dir/file3.txt", {st_mode=S_IFREG|0444, st_size=23411,
...}) = 0
getxattr("/share/dir/file3.txt", "system.posix_acl_access", (nil), 0) =
-1 EOPNOTSUPP (Operation not supported)
This does not only happen with ls. It happens with all commands that
want to read a certain directory (e.g. tar). A quick workaround is to
create a new file in the directory where it loops.
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 18:36 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 [this message]
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
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=413F5127.5030008@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.