Inodes

[Ric Urrutia]

In article <TALE.89Mar7015647 at imagine.pawl.rpi.edu> tale at pawl.rpi.edu writes:
>We have a semi-weird situation on situation in our devlopment
>directory here 
>...
>...
>The situation is this: /develop has four subdirectories names
>consult1.[1|2|3|4].  consult1.1 and .3 both are fine, but consult1.2
>and .4 have a problem with ..: getwd() can't open it, which breaks a
>lot of things that normally would happen in a directory tree, from a
>simple pwd to trying to compile with -g.  Now, I know why those things
>break so please don't explain it.  The problem is what the heck is
>wrong with /develop/consult1.[2|4]/..?  The inode number appears
>consistent (shares the inum of .) and the number of links are correct.
>Additionally, fsck didn't turn up anything; it things the whole system
>is just ducky.  
>


You say that /develop/consult1.2/.. shares the same inum as .  This is
your problem.  The .. directory should be linked to the parent directory
(/develop) and the . directory should be linked to /develop/consult1.2.
your best bet is to copy all the files in these directories to a new 
directory, remove consult1.[24], and rename the new directories.
wo