Paul_O'Neill@adc.com writes:
We have a NFS file system exported from our filer (it is also a CIFS shared folder). One of the sub-directories in this file system has duplicate files and directories. The duplicated files and directories have the same inode number. See the example below:
#ls -i 758588 NPR1/ 758583 docs/ 758588 NPR1/ 758583 docs/ 758587 README.version 758584 images/ 758587 README.version 758584 images/ 758586 bin/ 758585 licensing/ 758586 bin/ 758585 licensing/ 758582 cgi/ 758589 nprinfo 758582 cgi/ 758589 nprinfo
One thing I would check on any future occurrence of the problem is what "ls -f" shows on the directory, i.e. displaying the entries in directory order. There are two fairly likely possibilities: an A A B B C C D D order or an A B C D A B C D one. It would be a useful clue to where the bug is.
[... various ways of making the problem go away snipped ...]
Why is this problem happening? How do I stop this from happening?
Netapp suggests using snoop to try and capture this problem, but they have not told us what they are looking for.
I would imagine they want to see what the READDIR(PLUS) responses to the client actually look like, to distinguish between an ONTAP bug (filer duplicating the entries in its response) and a client one (possibly an incorrect replay from the directory cache).
We are also seeing this issue on more than one Solaris 8 box. Has anyone seen this issue before?
Certainly I haven't, and we use Solaris 8 clients. Some obvious questions: which ONTAP release are you using? What patches are on your Solaris 8 clients, and especially which versions of the kernel patch (108528-xx) and NFS patch (108727-xx)?
Chris Thompson Email: cet1@cam.ac.uk