Xref: utzoo comp.sys.att:5986 comp.unix.wizards:15308
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsd!sdcsvax!ucsdhub!hp-sdd!ncr-sd!ncrcae!wescott
From: wescott@ncrcae.Columbia.NCR.COM (Mike Wescott)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Re: find: bad status-- /u/tu
Message-ID: <4341@ncrcae.Columbia.NCR.COM>
Date: 30 Mar 89 16:30:34 GMT
References: <948@rush.howp.com>
Reply-To: wescott@ncrcae.Columbia.NCR.COM (Mike Wescott)
Organization: NCR Corp., Engineering & Manufacturing - Columbia, SC
Lines: 21

In article <948@rush.howp.com> bob@rush.howp.com (Bob Ames) writes:
> /u/tutor/Filecabinet/Profiles/9600bps:A2
> find: bad status-- /u/tutor/Filecabinet/practice/sample6.clf
> /u/tutor/.history
> find: bad status-- /u/hello

> The bad status messages continue for the rest of the /u directory.

One of the directories that find goes through right before the "bad status"
messages start probably has a ".." that is not the parent that find used
to get to the directory.

Try this in /u and some other directories:

	ls -id . */..

Each time you should get the same inode number for each directory.  Any
mismatch causes find to take the wrong path in trying to get back to where
it started from.

You can use /etc/link and /etc/unlink to fix.