find: bad status-- /u/tu

[Lloyd Kremer]

In article <948 at rush.howp.com> bob at rush.howp.com (Bob Ames) writes:

>3.51#
> /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.
>This all started after we brought the machine back from ATT for a
>new power supply |-)

In article <1287 at jhunix.HCF.JHU.EDU> ins_anmy at jhunix.HCF.JHU.EDU (Norman Yarvin) writes:

>I have exactly the same problem with my filesystem in the neighborhood of
> /usr (in places where I have made changes.)  "find" seems to be the only
>program affected, but I use "find".  I'm also using version 3.51 of the
>operating system.
>Yes, I got a new power supply too. :-?

In article <4341 at ncrcae.Columbia.NCR.COM> wescott at ncrcae.Columbia.NCR.COM (Mike Wescott) writes:

>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.


Yes, and after unlinking and linking the relevant directories, and everything
appears to be correct in the 'ls -id' tests, it would be very wise to unmount
and 'fsck -y -D' the affected filesystem.  Your repairs may be incomplete,
or the filesystem may have other problems of which you are not (yet) aware.
It may avoid some nasty surprises in the future.

Also, is there some correlation between power supply replacement and
filesystem corruption?  I sync there might be.  :-)

					Lloyd Kremer
					{uunet,sun,...}!xanth!kremer