Hi All,

Has anyone seen poor sybase response (well, totally maxed out CPU wise) at the same time as very high namei/s stats from the unix sar tool?

From sar info, namei/s = number of file system path searches per second. If namei does not find a directory name in the DNLC, it calls iget to get the inode for either a file or directory. Hence, most igets are the result of DNLC misses.

But, I can't think of any reason why a sybase server would suddenly start doing alot of file system path searches?

Any thoughts?