Re: PROBLEM: [2.6.22.1] Copying to full NFS dir

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Raphael Manfredi <Raphael_Manfredi@...>
Cc: <linux-kernel@...>
Date: Wednesday, August 1, 2007 - 12:31 pm

On Wed, 2007-08-01 at 17:00 +0200, Raphael Manfredi wrote:

The answer appears to be that some filesystems really _suck_ when they
have to return errors: they take forever to return to the user. When the
client then tries with several WRITE requests (it can cache huge numbers
of requests) then the cumulative effect of the delays are quite
noticeable as you can see above.

I've got a tentative client-side patch to deal with this sort of server.
Basically, when the client sees that a cached write returns an error,
then it will stop caching, and start doing O_SYNC-style writes until the
error conditions stop. That won't fix the server side problem, but it
does ensure that the application gets notified of the error as soon as
possible.

Cheers
  Trond
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
PROBLEM: [2.6.22.1] Copying to full NFS dir, Raphael Manfredi, (Wed Aug 1, 11:00 am)
Re: PROBLEM: [2.6.22.1] Copying to full NFS dir, Trond Myklebust, (Wed Aug 1, 12:31 pm)