Hi,
I've met a strange problem when simple open(2) on a file located in automounted directory can fails with ENOENT error although the file and directory are both present and accessible. I have a single NFS server and around 20 hosts accessing it. The problem is sometimes reproducible when all these hosts open log files on the server more or less simultaneously. The server (sqa1) exports the following: # cat /etc/dfs/sharetab /export - nfs rw /export/home3 - nfs rw The files are located in /export/home3/dm123456 directory, they are accessed by /net/sqa1/export/home3/dm123456/... path. And here what happens on the server: 97 0.00026 sqa60 -> sqa1 MOUNT3 C Mount /export 98 0.01101 sqa1 -> sqa60 MOUNT3 R Mount OK FH=E56D Auth=unix 107 0.00941 sqa60 -> sqa1 NFS C LOOKUP3 FH=E56D home3 108 0.00017 sqa1 -> sqa60 NFS R LOOKUP3 OK FH=C06D 109 0.00024 sqa60 -> sqa1 NFS C LOOKUP3 FH=C06D dm123456 113 0.00636 sqa1 -> sqa60 NFS R LOOKUP3 No such file or directory ... 154 0.00056 sqa60 -> sqa1 MOUNT3 C Mount /export/home3 155 0.00204 sqa1 -> sqa60 MOUNT3 R Mount OK FH=AA7C Auth=unix 163 0.00072 sqa60 -> sqa1 NFS C ACCESS3 FH=AA7C (read,lookup,modify,extend,delete) 164 0.00014 sqa1 -> sqa60 NFS R ACCESS3 OK (read,lookup,modify,extend,delete) 165 0.00076 sqa60 -> sqa1 NFS C LOOKUP3 FH=AA7C dm123456 166 0.00023 sqa1 -> sqa60 NFS R LOOKUP3 OK FH=49D1 For me it looks like the first lookup of export/home3/dm123456 failed and the second lookup succeeded, so the first open completed with ENOENT. Is this possible? Thanks, Dmitry This message posted from opensolaris.org
