Hi all, We're having an odd problem with a SNFS (cvfs) filesystem on one of our systems, call it X. If you don't know, SNFS is a shared filesystem that uses separate metadata servers. Since we have so many systems that access the same filesystem, we have a system identical to the one with the problem, for redundancy purposes. The control system, call it Y, doesn't have this problem.
Here's the gist, and I'm simplifying this down to the essentials. Say the filesystem is mounted as /foo/bar. Under that is a directory duh and in that is a file f, so /foo/bar/duh/f. On system Y, that file is visible and accessible, no problems. On system X, doing a "/bin/ls /foo/bar/duh" (or "cd /foo/bar/duh; /bin/ls") lists file f but any command that tries to access the file (e.g. via a stat, open, etc. system call) fails saying file not found. I've been using dtrace to try to determine what is happening in the kernel during one of these system calls and, specifically, I've been looking at the lookup*at kernel functions, but so far I've not been able to find much. At this point I'm somewhat stumped as to how to approach the problem further. While I'm not looking for a script from anyone, I would appreciate any advice on how to figure out why the kernel (snfs/cvfs driver?) is not able to access the file from system X. Remember that I can use system Y as a control system. Thanks, Justin
_______________________________________________ dtrace-discuss mailing list [email protected]
