You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Aaron Cammarata <aa...@ajcgames.com> on 2011/10/18 01:42:52 UTC
Reporting an error
Hello all -
I've encountered an error that asked me to send the details to this email.
I had a 1.6 working copy, and upgrade to Tortoise v1.7.n.
During the 'upgrade working copy' step, the disc ran out of space.
I cleaned up space and tried upgrading the WC again, and now when I try to
commit, I get:
---------------------------
Subversion Exception!
---------------------------
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
(users@subversion.apache.org)
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html
Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\wc_db.c'
line 7393: internal malfunction
---------------------------
OK
---------------------------
I'm guessing the best next step is delete and re-update from the repo?
--
Aaron <http://www.gablinga.com>
Re: Reporting an error
Posted by Aaron Cammarata <aa...@ajcgames.com>.
HI Daniel and Stefan -
Thank you for the reply, and for confirming that a checkout was the correct
next step.
I'm afraid I already deleted the wc.db file (see, "Out of disk space" ;), so
no chance to debug it.
It's possible that it was a valid 1.6, but since I had only 1.7 tools
(tortoise), I didn't get a chance to test it. Thanks for the thought,
though.
Best,
Aaron
On Tue, Oct 18, 2011 at 3:33 AM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
> Stefan Sperling wrote on Tue, Oct 18, 2011 at 11:11:22 +0200:
> > On Mon, Oct 17, 2011 at 04:42:52PM -0700, Aaron Cammarata wrote:
> > > Hello all -
> > >
> > > I've encountered an error that asked me to send the details to this
> email.
> > >
> > > I had a 1.6 working copy, and upgrade to Tortoise v1.7.n.
> > >
> > > During the 'upgrade working copy' step, the disc ran out of space.
> >
> > Oh, interesting. It's quite possible that 'svn upgrade' doesn't handle
> > this properly. But if something really bad happens, like if the sqlite DB
> > gets trashed in some way because of this, svn won't ever be able to
> recover.
> >
>
> But the working copy would likely remain a valid 1.6 working copy.
>
--
Aaron <http://www.gablinga.com>
Re: Reporting an error
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Stefan Sperling wrote on Tue, Oct 18, 2011 at 11:11:22 +0200:
> On Mon, Oct 17, 2011 at 04:42:52PM -0700, Aaron Cammarata wrote:
> > Hello all -
> >
> > I've encountered an error that asked me to send the details to this email.
> >
> > I had a 1.6 working copy, and upgrade to Tortoise v1.7.n.
> >
> > During the 'upgrade working copy' step, the disc ran out of space.
>
> Oh, interesting. It's quite possible that 'svn upgrade' doesn't handle
> this properly. But if something really bad happens, like if the sqlite DB
> gets trashed in some way because of this, svn won't ever be able to recover.
>
But the working copy would likely remain a valid 1.6 working copy.
Re: Reporting an error
Posted by Stefan Sperling <st...@elego.de>.
On Mon, Oct 17, 2011 at 04:42:52PM -0700, Aaron Cammarata wrote:
> Hello all -
>
> I've encountered an error that asked me to send the details to this email.
>
> I had a 1.6 working copy, and upgrade to Tortoise v1.7.n.
>
> During the 'upgrade working copy' step, the disc ran out of space.
Oh, interesting. It's quite possible that 'svn upgrade' doesn't handle
this properly. But if something really bad happens, like if the sqlite DB
gets trashed in some way because of this, svn won't ever be able to recover.
> In file
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\wc_db.c'
> line 7393: internal malfunction
This is due to invalid DB state.
Since you already know it happened while you ran out of disk space
there is not much point in trying to debug it. However, if you want
to share your .svn/wc.db file (privately if you like) I could take
a look and try to at least determine what exactly is wrong in the DB.
Maybe we can somehow prevent the inconsistency from occurring.
> I'm guessing the best next step is delete and re-update from the repo?
Yes, you should get a fresh checkout.