From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleg Drokin Subject: Re: nfsd-fh: found a name that I didn't expect Date: Mon, 31 Mar 2003 13:05:40 +0400 Message-ID: <20030331130540.J25533@namesys.com> References: <20030331123705.F25533@namesys.com> Mime-Version: 1.0 Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com Content-Disposition: inline In-Reply-To: List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Soeren Sonnenburg Cc: Soeren Sonnenburg , reiserfs-list@namesys.com Hello! On Mon, Mar 31, 2003 at 10:43:56AM +0200, Soeren Sonnenburg wrote: > > > > > Yes of course I am. I hope the other admins won't kill me, but I guess they > > > > > know that I willing to do experiments from time to time ;-) > > > > > Could something worse happen when I try the patch, that could not be fixed by > > > > > simple rebooting ? > > > > See the patch below. > > > > It should not break anything. > > > Well, we keep getting this error in massess too... and in our case it is > > > very likely that clients access the same file from all the clients... > > Are all of your NFS exports where these errors happens reiserfs? > This is the same machine I was telling you about on lkml ... Ah, ok. > well, I can't do experimental testing as there are like 40 > diskless machines using > that disk ... I could somewhen in the evening/night do some stress test > but thats it... Ok, I understand. Well, I guess I will spend some time on this iget5 2.4.20 backport and on trying to reproduce the problem locally. Bye, Oleg