On a recent kernel: # mount -tnfs4 pearlet1:/ /mnt/ # find /mnt/ /mnt/ find: File system loop detected; `/mnt/DIR' is part of the same file system loop as `/mnt/'. Here /mnt/DIR is a server-side mountpoint, hence has a different fsid than /mnt/. Wireshark confirms that the server is returning a different fsid. However, 'strace -v find /mnt/' shows stat returning st_dev=makedev(0, 22) for both /mnt and /mnt/DIR. If I then do a 'ls /mnt/DIR', followed by another find, the error goes away, and this time an strace shows that stat is returning (0, 23) for /mnt/DIR. I don't see any obvious problem with the network trace, so it looks to me like the client is failing to recognize the mountpoint when it should? --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
