We are investigating this issue internally. We have reproduced it. Our intial investigations show that the Digital Unix client sends a readdir request and we respond to it. We mark in our reply that we are not at the end of the directory, but the client never comes back for more. Our suspicions are that the client is deciding it has all of the directory information based on some client side cached information or the cookie we pass back. We have not yet determined with certainty whether it is a client or server bug.
John Edwards Member of Technical Staff Network Appliance
On Thu, 17 Sep 1998, Christoph Doerbeck wrote:
Naturally, the first response from Digital is that it is likely to be a NetApp problem, and the first response from NetApp is that it is likely to be a Digital Unix problem. Any suggestions on how to determine where the problem lies?
I would guess that if you exported a filesystem from a SUN, and could repeat the problem on the DEC box, you would have good ammo to chew out someone at DEC. If the Sun export works, then start chewing on NetApp.
!#/bin/csh # a few modifications (use lptest instead of printcap)
set num=0 while ( $num < 100 ) @ num = $num + 1 lptest > reallyreallyverylongnamedatafile.$num ln -s reallyreallyverylongnamedatafile.$num 1.$num echo "$num is done" end echo "And the magic answer is..." ls | wc exit
On sparc 20, mounting from a F330 running 4.0.1c: dunsel% ls | wc 201 201 4119
- Christoph
- Hey greg, remember dunsel???