Ok, well I have found very good success in killing this stupid stale file handle problem in the 2.6.11 kernel by switching from ext3 to ext2 and then rebooting. For the past 5 days not 1 of my developers has complained about this issue.
Obviously if this machine goes down and a fsck starts running on the 750 GB of data, I am in some deep doo doo, but for now I am using this as a way of getting around the problem until someone comes up with a nifty patch.
-Kris

On Tue, 2005-05-03 at 22:44, Frank Steiner wrote:

Kris Vassallo wrote

> So in reference to this bug
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150759
> it seems as if ridding the system of the journal by instead using ext2
> is fixing the problem? I can't tell if that bug has anything to do with
> providing ESTALE errors but it seems to have the same effect where you
> can't see files even though they are there. 

Yes, sounds very similar...


> 
>  Has anyone tried using the journal_data_ordered option? I am not sure
> there is a way to do that in reiser but I know it can be done with ext3.

According to the man page, "data=ordered" is the default. Have you
explicitely changed it?

I couldn't find any option to change this in reiserfs...