Thank you to all who responded. I received lots of helpful hints.
I haven't fixed my problem yet, but am acting upon one response that may
be the answer. I wanted to post this partial summary in the mean time.
When I find the real answer, I will re-post. Thanks again.
_________________________________________________________________________
The original question had to do with my cron job:
> find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune
>
>producing the following output:
>
>find: cannot stat /home/qa: No such file or directory
>find: cannot stat /bin: No such file or directory
>find: cannot stat /lib: No such file or directory
>find: cannot stat /sys: No such file or directory
>find: cannot stat /.cshrc: No such file or directory
>find: cannot stat /.login: No such file or directory
>find: cannot stat /.profile: No such file or directory
>find: cannot stat /.rhosts: No such file or directory
>find: cannot stat /vmunix.org: No such file or directory
>find: cannot stat /kadb: No such file or directory
>find: cannot stat /boot: No such file or directory
>etc.,etc. (about 50 more local and nfs entries)
The responses were all pretty good ones. Several people were experiencing this
problem presently, mostly on Solaris 2.1 machines, and were eager for my summary. Some mentioned automounted files, but I'm not running automount. Sorry for not mentioning that before.
Most felt:
- There was a permissions problem reading nfs mounted files.
- Problem with underlying mount permissions.
- Symbolic links pointing nowhere.
- Bad hard link in the parent directory.
None of these, however, explain files such as /.cshrc, /.login, etc. I did
checked the suggested permissions, anyhow, to verify that they were alright.
!!HOWEVER!!
Lothar Mueller from Darmstadt, Germany sent the following:
> Do a filesystem check on the root - filesystem ! Looks like somthing with
> your disk is going wrong. We once had the same error at one of our servers
> (a 3/280) and ended up with a new eagle-disk.
> Much luck !
This revealed a problem. (Paraphrasing):
"CLEAN FLAG WRONG IN SUPER-BLOCK: ok to fix? Y or N"
I answered "Y" and ran fsck again. The error was still there. Repeatedly, it
would not fix. I may have a disk problem, which I am persuing at the moment.
I will post the real answer when the problem is fixed.
Thanks again to all.
Bob Hudson
IDE Corporation
San Francisco, CA
bobh@ide.com
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:52 CDT