rich@jolnet.UUCP (Rich Andrews) (08/01/88)
When I am in /usr/lib and execute a find command such as "find . -print" it gets to /usr/lib/uucp and then it fails with a stat() failed /usr/lib/uucp/cd_text. This is not the only file that this happens to. It also happens to some of my /usr/lib/*.a files and to some of my F77 libs and pascal files. Fsck reports all is ok and the files are readable. Any ideas? rich andrews -- Any opinions expressed are my own. Now, for a limited time, they can be yours too, for the incredible price of only $19.95. Simply send $19.95 (in Alterian dollars) to ...ihnp4!killer!jolnet!rich.
hd@mh_co2.mh.nl (Theo Hardendood) (08/01/88)
From article <673@jolnet.UUCP>, by rich@jolnet.UUCP (Rich Andrews): > When I am in /usr/lib and execute a find command such as > "find . -print" it gets to /usr/lib/uucp and then it fails > with a stat() failed /usr/lib/uucp/cd_text. > (...) > Fsck reports all is ok and the files are readable. > Any ideas? Yes, we had the same problem on one of our own machines. The problem was a corrupt parent directory. As you will probably now, fsck does not check the contents of files so it will report no errors. Try checking the file system with 'ncheck -a <file-system>'. If this doesn't help, examine /usr, /usr/lib and /usr/lib/uucp with 'ls -il' or 'od -c <directory-name>'. Regards, Theo Hardendood Theo Hardendood hd@mh.nl via european backbone (mcvax) Multihouse NV, Gouda - The Netherlands uucp: ..!mcvax!mh.nl!hd "A conclusion is simply the place where someone got tired of thinking."