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

Bug Report: VisualSVN Upgrade Project: "Insufficient NODES rows for 'C:\...\.svn\tmp\wcng\...'"

From: Andre Light <alight_at_eskillz.com>
Date: Thu, 13 Oct 2011 00:19:04 -0500


When upgrading my TortoiseSVN solution from v1.6.x (latest stable release according to VisualSVN) to v1.7.0 using the VisualSVN "Upgrade Working Copy" menu command, I received an error:

Insufficient NODES rows for 'C:\[SolutionDirectory]\.svn\tmp\wcng\[Project Directory Within Solution]'

Here's a screenshot of the VisualSVN Error:


I actually got the upgrade to work, so I hope the following information will help you fix the bug more quickly (though I don't know if what I did was a good solution).

While searching for the issue online, I came across this page: http://www.mail-archive.com/commits@subversion.apache.org/msg08133.html

That helped me see the code which I'm guessing was throwing the error:

- if (have_base
- && (base_presence == svn_wc__db_status_normal
- || base_presence == svn_wc__db_status_incomplete))
- {
- apr_hash_t *props = revert_props ? revert_props : base_props;
+ /* Need at least one row, or two rows if there are revert props */
+ if (top_op_depth == -1
+ || (below_op_depth == -1 && revert_props))
+ return svn_error_createf(SVN_ERR_WC_CORRUPT, NULL,
+ _("Insufficient NODES rows for '%s'"),
+ svn_dirent_local_style(
+ svn_dirent_join(dir_abspath, local_relpath,
+ scratch_pool), scratch_pool));

So, I took a look inside the .svn folder indicated by the path after ...\wcng\..., or C:\[Solution Directory]\[Project Directory Within Solution]\.svn. I opened the "dir-prop-revert" file in that folder, and the only contents were the word "END" and a line break. I found a total of 3 of those files with the same content in my entire Visual Studio 2008 solution (maybe remnants from unsuccessful commits, or some other issue?). By renaming all of them, the upgrade to TortoiseSVN v1.7.0 finally proceeded without any further issues. I committed and all seemed to be working properly.

FYI, before I upgraded TortoiseSVN and VisualSVN/VisualSVN Server, I committed all changes and performed a Cleanup Working Copy command as VisualSVN suggested. Also, I was currently within a branch, not the trunk.

I hope that information helps you all resolve a potential issue.

Thank you,


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

Received on 2011-10-13 07:33:57 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.