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

corrupt tree/transaction

From: Php freaked <phpfreaked9_at_gmail.com>
Date: Thu, 22 Apr 2010 14:54:33 +0200

Hello

I was using subversion until it reported me it ran out of disk-space. It
turns out the svn repository was configured at the smallest disk, so
logically I move the svn repository to other hard-drive. But ever since I
move it I've been unable to commit in my repository. To give you an idea of
what I did:

cp /path/to/oldrepository/ /path/to/newrepository/
mv /path/to/oldrepository/ /path/to/oldrepository2/ //for
backup purposes
mount --bind /path/to/oldrepository/ /path/to/newrepository/

By mouting the folder to a folder I could preserve all existing
configuration paths. As one can see I used the 'cp' command to copy the
files, I was told in #svn_at_freenode.net I should have used svn hotcopy. At
the time I was unaware of this, I presumed svn worked atomically on it's
files. After that I initially tried to commit my files and I received the
error 'Commit failed (details follow):Cannot write to the prototype revision
file of transaction '228-1' because a previous representation is currently
being written by this process'

I checked if there was such a transaction open using svnadmin lstxns And it
reported me there was indeed a transaction open but this one was 154-1. So I
removed the transaction, somewhere hoping it would resolve the issue but as
expected it didn't work. So somebody from the irc channel suggested me to
try dump/load to a clean repository, which i did.

svnadmin create /path/to/newrepo2/
svnadmin dump /path/to/newrepo/ -r 0:227 > backup.dump
svnadmin load /path/to/newrepo2/ < backup.dump

After that I tried to commit some files e.g. I did a svn checkout, reapplied
my changes and tried to commit them. Either in partial commits or multiply
files at once the error persists. I've already tried removing pending
transactions, the /db/revprops/228 appears not the be in there. What should
I do? Here's some additional information: rev 0-227 historical commits, rev
228 last working revision, 229 would be the supposed new revision.

Thanks in advance,

Lawrence
Received on 2010-04-22 16:24:26 CEST

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.