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

Re: Repository left in unusable state?

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-05-30 15:47:02 CEST

On 5/28/07, Sidney Cadot <sidney.cadot@jigsaw.nl> wrote:
> Hi all,
> This afternoon I ran out of disk space during a big commit (>100 MB worth of
> binary files).
> I have cleared out plenty of disk space now on the server, but it seems that
> the affected FSFS repository is left in a weird state. Whenever I try to do
> even small commits, I get the following:
> =====
> $ svn commit build-all.sh -m "Added build-all.sh script."
> Adding build-all.sh
> Transmitting file data .svn: Commit failed (details follow):
> svn: Cannot write to the prototype revision file of transaction '53-1'
> because a previous representation is currently being written by this process
> =====
> Plase note that this is a rather unhelpful message - perhaps understandable
> to the developer who wrote the code that emits it, but not to a user such as
> myself. What is "a representation" ? What is "this process", here? I get no
> indication on how to solve the problem.
> Second, I'd like to get my repository back in a working state. I tried the
> usual suspects; "svn cleanup", "svnadmin recover"; I looked for stale locks
> and transactions (none). Still, no luck.
> Does anybody have any ideas?

Have you tried restarting the server?



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 30 15:47:22 2007

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

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