> When doing a ls from a client on a exported XFS in a big directory
> (e.g. linux/fs/xfs) it gets into an endless loop and runs until the
> memory of the ls is exhausted. It shows the first entries normally
> and then returns one again and again.
I have my suspicions about the readdir interface at the moment, I have seen
rm -r -f miss a file. Also Suse just won another prize, 'First to NFS export
an XFS filesystem from Linux'! We have been busy making this thing stay up at
all, kernel builds inside XFS only started working this week.
We found problems between the Linux glibc getdents call running over NFS
to an XFS filesystem on Irix - which could be related, in that case it
managed to miss some entries. The getdents library call does this heuristic
to prune down the user's request size (since kernel getdents are bigger than
glibc getdents structures). In the case where it guesses wrong it does an
lseek backwards, this gets confused by the lseek offsets.
You could be hitting a similar problem.
Thanks for the update,