SVN Error - Filesystem is corrupt #49777

New Issue

There was some major corruption from the server side, so we ended up reverting repository to an older working state. We were not able to recover your commits and now repository corresponds to revision 2958.

You'll have to re-checkout the repository and apply your latest changes again.

Afraid that's as much as we can do here.

There was some major corruption from the server side, so we ended up reverting repository to an older working state. We were not able to recover your commits and now repository corresponds to revision 2958. You'll have to re-checkout the repository and apply your latest changes again. Afraid that's as much as we can do here.

Yevgeny Makarov commented

2016-10-19 20:29:23 +02:00

Changed status from 'Resolved' to: 'Open'

Yevgeny Makarov reopened this issue

2016-10-19 20:29:23 +02:00

Yevgeny Makarov commented

2016-10-19 20:29:23 +02:00

Again, it is the same.

Sergey Sharybin commented

2016-10-19 21:50:33 +02:00

That is weird.

What is your client, it's version and what exactly you're doing when this happens?

That is weird. What is your client, it's version and what exactly you're doing when this happens?

Yevgeny Makarov commented

2016-10-19 22:02:03 +02:00

SmartSVN 9.1.2
I made a lot of similar commits before and had no problems.

SmartSVN 9.1.2 I made a lot of similar commits before and had no problems.

Sergey Sharybin commented

2016-10-19 22:41:28 +02:00

Well, it is second time your commit causes a server corruption, so it's something definitely not right here.

It is quite late here, so for now i've simple reverted the repository to an older state. See the list for details.

I've also revoked commit rights from you for until we go to the root of the issue to prevent any possible further corruption. Please join #blendercoders IRC room at irc.freenode.net tomorrow CEST office hours and poke hackerman-. We'll go over your setup and probably try several commits to a test repository.

At the meantime, if you can archive your current bf-manual checkout and share with me (via ftp.blender.org/incoming maybe?) that will give us some extra info to look into and hopefully figure out what the exact issue is.

Well, it is second time your commit causes a server corruption, so it's something definitely not right here. It is quite late here, so for now i've simple reverted the repository to an older state. See the list for details. I've also revoked commit rights from you for until we go to the root of the issue to prevent any possible further corruption. Please join `#blendercoders` IRC room at `irc.freenode.net` tomorrow CEST office hours and poke `hackerman-`. We'll go over your setup and probably try several commits to a test repository. At the meantime, if you can archive your current bf-manual checkout and share with me (via ftp.blender.org/incoming maybe?) that will give us some extra info to look into and hopefully figure out what the exact issue is.

Aaron Carlisle commented

2016-10-19 23:28:50 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2016-10-19 23:28:50 +02:00

For the record I use the same SVN client

Sergey Sharybin commented

2016-10-21 09:53:50 +02:00

Just a quick update. this is a bug in svn itself which i'm forwarding to svn developers now. For the time being please avoid big changes to svn repositories since recovering from a broken state is quite tedious and time consuming..

Will give more information when we have it.

Just a quick update. this is a bug in svn itself which i'm forwarding to svn developers now. For the time being please avoid big changes to svn repositories since recovering from a broken state is quite tedious and time consuming.. Will give more information when we have it.

Sergey Sharybin commented

2016-10-25 17:01:38 +02:00

Just a quick update: the bug was confirmed by SVN developers and being worked on. There is an initial fix for it committed which fixes this particular corruption.

So seems it'll be included into upcoming 1.9.5 release which is planned real soon AFAIK.

Just a quick update: the bug was confirmed by SVN developers and being worked on. There is an initial fix for it committed which fixes this particular corruption. So seems it'll be included into upcoming 1.9.5 release which is planned real soon AFAIK.

Aaron Carlisle commented

2016-10-29 03:33:09 +02:00

Please forgive me, but this time it was my fault please reset the repository to rBM2977

Erick Tukuniata commented

2016-11-08 20:53:23 +01:00

Added subscriber: @ErickNyanduKabongo

Erick Tukuniata commented

2016-11-08 20:53:52 +01:00

Any news here?

Sergey Sharybin commented

2016-11-10 12:07:38 +01:00

No real news unfortunately.

This is a bug in Subversion itself which was fixed in the upstream. Now we just wait for Subversion 1.9.5 to be out (which was actually planned at end of Oct but was delayed after that).

No real news unfortunately. This is a bug in Subversion itself which was fixed in the upstream. Now we just wait for Subversion 1.9.5 to be out (which was actually planned at end of Oct but was delayed after that).

Aditia A. Pratama commented

2016-11-22 13:57:41 +01:00

Added subscriber: @AditiaA.Pratama

Aditia A. Pratama commented

2016-11-22 13:57:41 +01:00

I've stumble this error, I don't know if this related with this issue

svn: E175009: The XML response contains invalid XML
svn: E130003: Malformed XML: no element found

I've stumble this error, I don't know if this related with this issue ``` svn: E175009: The XML response contains invalid XML svn: E130003: Malformed XML: no element found ```

John Roper commented

2016-11-22 14:23:31 +01:00

Added subscriber: @JohnRoper