FS processing error

722 views
Skip to first unread message

Manuel

unread,
Jun 11, 2015, 9:48:46 AM6/11/15
to us...@tortoisesvn.tigris.org
Hey guys,

I'm new here, and unfortunately all I have to offer right now is a problem with my Tortoise... I hope this is the right forum and maybe someone is willing to help me.

This is our setup:
We have an FS repository running on a network drive to share it easily with different users. We are all running Win7, but not the same Tortoise version. But, this does not seem to be the problem.
In my case, I am running TortoiseSVN 1.8.3 with Subversion 1.8.4.

Suddenly, a few months ago we get an error message when committing to one specific repository.
It says: "post commit FS processing had error: Couldn't open rep-cache database". (https://dl.dropboxusercontent.com/u/1436404/SVNerror.PNG)
But committing and updating generally works fine. But we are a little bit afraid that at some point it won't work anymore so we would like to solve the problem. Does anyone have an idea what one could do?

If not, we would just copy the files and create a new repository...

Thanks in advance!
Jamo

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3122069

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

Simon Large

unread,
Jun 11, 2015, 10:02:40 AM6/11/15
to us...@tortoisesvn.tigris.org
On 11 June 2015 at 14:40, Manuel <m.stein...@outlook.com> wrote:
Hey guys,

I'm new here, and unfortunately all I have to offer right now is a problem with my Tortoise... I hope this is the right forum and maybe someone is willing to help me.

This is our setup:
We have an FS repository running on a network drive to share it easily with different users. We are all running Win7, but not the same Tortoise version. But, this does not seem to be the problem.
In my case, I am running TortoiseSVN 1.8.3 with Subversion 1.8.4.

Suddenly, a few months ago we get an error message when committing to one specific repository.
It says: "post commit FS processing had error: Couldn't open rep-cache database". (https://dl.dropboxusercontent.com/u/1436404/SVNerror.PNG)
But committing and updating generally works fine. But we are a little bit afraid that at some point it won't work anymore so we would like to solve the problem. Does anyone have an idea what one could do?

If not, we would just copy the files and create a new repository...

Try running svnadmin verify on the repository (svn command line tools are shipped with TSVN 1.8.x). If it verifies OK then you need to set up a proper server and access the repo that way. DO NOT access the repository directly on a network share. At some point it will fail.

Simon

Manuel

unread,
Jun 12, 2015, 5:43:09 AM6/12/15
to us...@tortoisesvn.tigris.org
Hey Simon,

Thanks for your reply. We ran the test and got the same error. Additionally we got
"E200029: Couldn't perform atomic initialization"
"E20030: sqlite[11]: database disk image is malformed, executing statement 'PRAGMA synchrosnus = OFF...."

We tried some solutions to repair the nodes we found online, but it didn't work for us. Now, we simply created a new repository and all updated to the latest version of TortoiseSVN, hope this should solve it.

Jamo

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3122256

Simon Large

unread,
Jun 12, 2015, 6:07:23 AM6/12/15
to us...@tortoisesvn.tigris.org
On 12 June 2015 at 10:43, Manuel <m.stein...@outlook.com> wrote:
Hey Simon,

Thanks for your reply. We ran the test and got the same error. Additionally we got
"E200029: Couldn't perform atomic initialization"
"E20030: sqlite[11]: database disk image is malformed, executing statement 'PRAGMA synchrosnus = OFF...."

We tried some solutions to repair the nodes we found online, but it didn't work for us. Now, we simply created a new repository and all updated to the latest version of TortoiseSVN, hope this should solve it.


It may solve it for a while but unless you use a proper server process you leave yourselves wide open to further problems. You have been warned.

Simon
Reply all
Reply to author
Forward
0 new messages