On Thu, 2005-08-18 at 10:04 +0200, Hans P. Reiser wrote:
> The FAQ states that a working copy on NFS server works, and suggests
> disabling subtree checking if it does not. As it did not work in my
> environment, and disabling subtree checking was not an option, I
> tracked down the problem a bit closer:
Fascinating. I'm surprised that a filesystem problem of this magnitude
would be primarily noticeable in Subversion, and not in a host of other
cases.
> Subversion could use a simple workaround for such broken systems by
> calling ftruncate with size 0 after creating a new file. Any chance
> for such a subversion modification? As this question is already
> highlighted with a red box in the FAQ, it is surely a frequent
> issue.
I just looked at the FAQ and couldn't find a red box, nor did the
question about NFS refer to XML parse errors. So I'm a bit skeptical
that this is a frequent issue.
This would be a pretty easy workaround for us since file opens are
funneled through svn_io_file_open(). But it's always a bit dangerous to
introduce such workarounds into an application if the benefit is
marginal. It leeches performance from everyone else, and it's hard to
tell when we get to remove the workaround without creating a regression.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 18 16:48:05 2005