From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461)

Description of problem:
When a firs bash is in a directory, say ~/bin of your files, it becomes 
confused, if in another (second) shell ~/bin is moved to ~/bin2, and a cp -r 
~/bin2 ~/bin is issued.

$ mv ~/bin ~/bin2
$ cp -r ~/bin2 ~/bin


ls -i in the first shell will show the old inode numbers, as a side note 
executing a program from bin will not see the new versions of the files either, 
it will run the old executables.

ls -i in the second shell will show the right inode numbers.

So it seems the first bash is using files that aren't even in the file system 
anymore.  This was done on an ext3 journaled file system, in case that is where 
the problem acutally is.



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. cd ~/bin in one bash. Assume ~/bin has some files in it.
2. in another bash 
   a. mv ~/bin ~/bin2
   b. cp -r ~/bin2 ~/bin
   c. ls -i ~/bin
3.In original bash ls -i ~/bin
4. Note the different inode numbers.
    

Actual Results:  Old executables were being executed, after a cvs checkout, and 
recompile occured in another shell.  

Expected Results:  I think bash would access the files that are still in the 
filesystem.

Additional info: