SUMMARY: find does not stat sometimes

From: Keith M Willenson (
Date: Thu Jan 25 1996 - 14:21:45 CST

   Thanks to all who responded. The problem was indeed solved by fsck. The
cause was identified by Russ Poffenberger. I had forced a link between
directories (if its not supposed to happen then why have an option for it?)
just before these symptoms appeared. Even after removing the link the
symptoms remained. No reboot of the machine was needed after the fsck.

Thanks to: (Bismark Espinoza) (Kevin Sheehan {Consulting Poster Child})
Andrew Lamb <> (Glenn Satchell - Uniq Professional Services) (Russ Poffenberger) (David Steiner)

Original posting:

find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune

produced the following output:

find: cannot stat /solaris/solaris_src/vtwm5.0: No such file or directory
find: cannot stat /solaris/solaris_src/bsd2svr4.h: No such file or directory
find: cannot stat /solaris/solaris_src/elm2.4: No such file or directory
        . (much stuff omitted)


Date: Fri, 19 Jan 96 13:41:08 PST
From: (Bismark Espinoza)

Do a fsck of the partition.

From: (Kevin Sheehan {Consulting Poster Child})
Date: Sat, 20 Jan 1996 17:34:50 EST

Is this perhaps NFS mounted soft??

                l & h,

From: Andrew Lamb <>
Subject: Re: find does not stat sometimes

Maybe one of the directories in the path is missing execute permission
for either group or others, or is owned by the wrong person/entity, causing
the down-tree files to be inaccessible to some programs/commands.

From: (Glenn Satchell - Uniq Professional Services)
Subject: Re: find does not stat sometimes

I would definitely be tempted to reboot the server and fsck that disk -
it looks like something is not too good. The clients may only be
looking through their local memory cache for file attributes.

Also you should plan to upgrade from 4.1.4 to something newer, either
4.1.4 if you need to maintain 4.1.x on the system or 2.4/2.5 if you can
go to Solaris. There were plenty of bugs in NFS and th efilesystem
fixed in later releases. Also from 4.1.2 onwards you get the fast fsck
feature which means reboots are much, much quicker.


Glenn Satchell            | There's  a fine  line
Uniq Professional Services Pty Ltd  ACN 056 279 335  | between  fishing  and
PO Box 70, Paddington, NSW 2021, (Sydney) Australia  | standing on the shore
Phone 02 380 6360 Pager 016 287 000 Fax 02 380 6416  | looking like an idiot.

Date: Mon, 22 Jan 96 07:08:49 PST From: (Russ Poffenberger) Subject: Re: find does not stat sometimes

It does sound like a filesystem problem of some sorts. If there was a hard link between directories, you can get this behavior because find will traverse into the directory from one path, but when it goes back up one directory, it follows the hard link back to the wrong place, where those files don't exist anymore.

You aren't supposed to be able to create hard links between directories, so it would indicate a filesystem problem. fsck would likely find it.

Russ Poffenberger Engineering Specialist Schlumberger Technologies ATE DOMAIN: 1601 Technology Drive CIS: 72401,276 San Jose, Ca. 95110 Voice: (408)437-5254 FAX: (408)437-5246

Date: Tue, 23 Jan 96 09:42:48 +0100 From: (David Steiner) Subject: Re: find does not stat sometimes


This sounds like the disk has been exported without the root option being set and there is no read permission for others. Without the root option in exports, the root user is mapped to user nobody on NFS partitions (as a security precaution). Since "nobody" receives the permissions set for others, others need read protection on the directories in question.

Hope it helps, -David-

David R. Steiner University of Vechta Research Assoc. _____ ___ ____ __ Remote Sensing/GIS // // // `` // | // === //='' //--| email: _//_ __// _//_ _//_ _|_ fax:(+49)4441-15445 Vechta, Germany

* All decisions are based on insufficient evidence. -Nickel Hunsenmeir *

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:52 CDT