brian@apt.UUCP (Brian Litzinger) (01/17/90)
I running ISC 386/ix UNIX V.3.2 and have run into the following
problem with find(1):
Find(1) reports the following errors while traversing part of one
of my filesystems: (I'm logged in as root)
# find . -print
[ lotsa of normal find(1) output followed by ... ]
find: stat() failed: ./brian/core: No such file or directory
find: stat() failed: ./leone: No such file or directory
find: stat() failed: ./chet: No such file or directory
find: stat() failed: ./zyrel: No such file or directory
find: stat() failed: ./marcos: No such file or directory
find: stat() failed: ./btest: No such file or directory
find: stat() failed: ./dmyers: No such file or directory
These directories seem alright. And a command like
# find chet -print
works as expected, however a command like
# find brian -print
works mostly through the directory then reports similar errors
near the end. The directory tree under brian is by far the
biggest of the user directories.
Is there some limit to the number of entries find(1) can process?
Or has the file system become corrupt in a way that bothers nothing
except find(1)?
<> Brian Litzinger @ APT Technology Inc., San Jose, CA
<> UUCP: {apple,sun,pyramid}!daver!apt!brian brian@apt.UUCP
<> VOICE: 408 370 9077 FAX: 408 370 9291
--
<> Brian Litzinger @ APT Technology Inc., San Jose, CA
<> UUCP: {apple,sun,pyramid}!daver!apt!brian brian@apt.UUCP
<> VOICE: 408 370 9077 FAX: 408 370 9291