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

RE: SVN corrupts repository when server runs out of disc space.

From: Taylor, Richard <rtaylor_at_t-tales.com>
Date: 2007-04-24 10:13:48 CEST

Ahh yes sorry.

We are using FSFS.
When I say 'corrupted the directory' mean the following. When the server
runs out of disc space during a commit and it errors at the point of sending
file X in directory Y. Any subsequent checkout, update or commit of the
repository will fail when it reaches an operation on directory Y.

The work around we are using is to use the TSVN repo browser and delete the
directory from the repository and then re-add the directory and it's
contents again.

I'd like to add this into the bug database so that it can be given some
consideration. I know running out of resources (disc, memory etc) is
difficult to handle but it may also be the case that changing where and how
the failed commit is cleaned (temp files removed etc) that enough free space
can be created to roll back the commit and leave the FSFS repo in a intact
state 99% of the time.


-----Original Message-----
From: Malcolm Rowe [mailto:malcolm-svn-dev@farside.org.uk]
Sent: 23 April 2007 15:28
To: Taylor, Richard
Cc: dev@subversion.tigris.org
Subject: Re: SVN corrupts repository when server runs out of disc space.

On Mon, Apr 23, 2007 at 01:45:31PM +0100, Taylor, Richard wrote:
> We have a RHEL4 64bit server running SVN 1.3.1. We are coming to the end
> a project and the server is nearly full. On 2 separate occasions the
> has run out of disc space during a commit and the server has corrupted the
> directory containing the file in the repository. Obviously the commit will
> fail if the server runs out of disc space but repository should probably
> remain unchanged.

What do you mean by 'corrupted the directory'? Are you referring to the
physical on-disk directory, or one of the directories modified by the

Secondly, are you using BDB or FSFS? Ah.. I was just going to say that
FSFS doesn't need to write files during the finalisation phase of a
commit (just rename them), but then I realised that it does need to
rewrite the db/current file... but from what I can recall, that should
just result in the commit failing, leaving an unreferenced revs/N and
revprops/N file. Hmm.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 24 10:14:03 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.