On Monday 02 June 2008 22:38:31 Bruce Wilson wrote: > I tripped over some of those "orphaned" problems which may have been > addressed by Alexander's 0007 patch, but in my case they all turned out > to be caused by "destroy permanently" and were disposable.
Hello, Just to clarify, patch 0007 does not fix any problems with orphans, it is in fact meant as an easy way to safely remove all such projects at once. It works by rewriting all actions that interact both with orphaned and live folders so that they don't touch orphans. It also runs an additional pass of action processing to find orphans that have some of their subfolders moved into the live area -- removing them would require rewriting one move action into multiple adds, which is way too complex and error-prone. In case of our repository, I found three causes of orphans: 1) Projects that I destroyed before the conversion. 2) Perhaps, some projects that were removed a long time ago (e.g. old releases), but which were linked to by newer projects. 3) Projects recovered from an archive. I didn't care about orphans from cases 1 and 2, and the third case is detected by the additional pass. Also, the main problem that I had with them was coming from the fact that all orphans are put into one big directory in the repository. It seems that Subversion cannot deltify directories, so every time a file in one of the orphans changes, it stores a complete list of the /orphaned folder. I estimated that if I didn't interrupt svnadmin, the final repository size would have amounted to more than 20GB. Without the orphans it's mere 1.6GB. Alexander. _______________________________________________ vss2svn-users mailing list Project homepage: http://www.pumacode.org/projects/vss2svn/ Subscribe/Unsubscribe/Admin: http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org Mailing list web interface (with searchable archives): http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
