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

Re: Receiving an error via an SVN repository

From: Ben Reser <ben_at_reser.org>
Date: Thu, 09 Jan 2014 14:26:17 -0800

On 1/9/14, 2:11 PM, Sinclair, Ronda D. wrote:
> We are running Tortoise SVN on a Windows 7 machine – and had some network
> issues were connectivity to our share where the repository was stored was up
> and down. We’ve had the user copy the files locally and they can access them
> and commit them but when trying to recommit them to the network repository they
> were getting a file lock error. The user was able to break the lock but now
> receives this error : Error: Can't set position pointer [...] : An attempt was
> made to move the file pointer before the beginning of the file and can’t
> reconnect to the SVN repository on the network.

Hard to make much of that. Can you post the full and exact error message (you
can ommit paths just don't ommit error codes and exact phrasing of the error
messages)?

Also it would probably be helpful to provide an exact version of Subversion
that you're using.

The one concern I do have is it sounds like you were putting the repo on a
network file share and then using ra_local (file:///) to access it. I wouldn't
recommend that. If you want to allow network access to the repository I'd
suggest using one of our server processes.

> I see this link to http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html
> to unwedge a repository but wanted to check to see if you had any
> recommendations on what to do before trying to do a restore of the repository
> or should we try the “unwedge” action first?

FSFS repos don't get wedged, is this a BDB repo?

Biggest suggestion I can make is make sure you are working off a copy of the
repo and not your only copy.
Received on 2014-01-09 23:25:58 CET

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.