[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 400 Bad Request - NFS attribute cache problem

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2007-04-13 13:08:13 CEST

On Thu, Apr 12, 2007 at 08:25:24PM -0400, Devin Bougie wrote:
> '-' is SL3, '+' is SL4. So it's opening a temporary file under
> the working area, writing 218 bytes to it, and immediately
> statting it. SL3 gets 218 bytes, SL4 gets 0. On SL3, the next
> step is to rewind the file, read 218 bytes, and send something
> (probably the same 218 bytes SSL encrypted) to the svn server.
> With the attribute cache on, the answer to the fstat64 comes out
> of the cache; with it off, the write has to commit and the fstat64
> round-trips to the server, so this is all looking consistent with
> an NFS attribute cache problem on SL4.

Seems like a duplicate of RedHat bug 194088; it may have been around for
a while.

Unfortunately, I can't give you any advice other that disabling
attribute caching - even adjusting for NFS's odd behaviour, we rely on
sane behaviour from write/fstat in more places than just this.


  • application/pgp-signature attachment: stored
Received on Fri Apr 13 13:08:40 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.