error while creating repository from dumpfile

hi all,
I have created the dumpfile for my repository ...and then
used svnadmin load
to create the repository out of the dumpfile.....I got the
following
error....
<<< Started new transaction, based on original
revision 6345
     * adding path : orphaned/_YGFBAAAA ... done.
     * adding path : orphaned/_YGFBAAAA/Report ... done.
     * adding path : orphaned/_ZHFBAAAA ... done.
     * adding path : orphaned/_ZHFBAAAA/ ... done.
     * adding path : orphaned/_NIFBAAAA ... done.
     * adding path : orphaned/_NIFBAAAA/App_ces ... done.
     * adding path : orphaned/_NJFBAAAA ... done.
     * adding path : orphaned/_NJFBAAAA/Service ... done.
     * adding path : orphaned/_RJFBAAAA ... done.
     * adding path : orphaned/_RJFBAAAA/Service ... done.
     * adding path : orphaned/_SJFBAAAA ... done.
     * adding path : orphaned/_SJFBAAAA/rService ... done.
     * adding path : orphaned/_WJFBAAAA ... done.
     * adding path : orphaned/_WJFBAAAA/Service ... done.
     * adding path : orphaned/_WJFBAAAA/M.....ade.d
iscomap ...svnadmin: File not found: revision 5831, path
'/orphaned/_UDBBAAAA/..///....sie.discomap'



any reasons why could this be and how to solve this????
Thank u in advance.....
-- 
View this message in context: http://www.nabble.co
m/error-while-creating-repository-from-dumpfile-tp16823841p1
6823841.html
Sent from the vss2svn - users mailing list archive at
Nabble.com.

_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.
pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/lis
tinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-c
ontrol.subversion.vss2svn.user

nandinicvs wrote:
> I have created the dumpfile for my repository ...and
then used svnadmin load
> to create the repository out of the dumpfile.....I got
the following
> error....
> <<< Started new transaction, based on original
revision 6345
> iscomap ...svnadmin: File not found: revision 5831,
path
> '/orphaned/_UDBBAAAA/..///....sie.discomap'
> 
> any reasons why could this be and how to solve
this????

Googling for:

"svnadmin: File not found" vss2svn

returns in the first few results this page: 
http://www.pumacode.org/projects/vss2svn/wiki/Fix
ingTheDumpfile

This is a manual approach which is good if you don't have
too many 
errors, or don't want to re-run the conversion.  If Bryan's
patches fix 
the source of the problem they're more ideal.

-Nathan

_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.
pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/lis
tinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-c
ontrol.subversion.vss2svn.user

Hello,

For the last two weeks I have been trying to convert our
project's VSS 
repository to SVN, and last Friday I finally succeded in
producing a 
Subversion repository, that does not deviate in it's final
state from the VSS 
one, and has reasonable coverage of the past history. Since
the part of the 
repository that I tried to convert has more than 10 years of
data on about 
30000 files, not counting branches, and, naturally, is a bit
corrupted, it's 
impossible to ensure 100% correctness anyway.

As the patches that I added in order to achieve that goal
might be useful for 
others, I want to share them here.

Of 11 patches, 4 address memory usage issues on large
repositories, 3 add 
enhancements to vss2svn, and 4 fix bugs.

Their description is as follows:

0001-Added-an-option-to-reuse-text-files-of-the-cache-for.pa
tch

  This patch adds an option, which, when activated, makes
vss2svn reuse 
temporary files left from previous runs, thus avoiding
costly calls to 
ssphys. It is useful during experimenting.

0002-Added-visual-progress-indication.patch

  Adds progress indication to most of the steps. 

0003-Reimplemented-LoadVssNames-to-use-XML-Parser-direct.pat
ch

  On our repository, loading the xml file via XML::Simple
consumes about 1GB 
of memory. That is unacceptable, so this patch reimplements
that step to use 
XML::Parser. I'm not familiar with it, so I might have
missed some difficult 
cases, e.g. maybe handling things like "&"
in names.

0004-Use-arrays-for-table-data-storage-in-order-to-avoid.pat
ch

  Use array of arrays instead of an array of hashes to hold
entries in 
MergeParentData, to save some memory. 

0005-Use-a-sliding-window-limited-by-timestamp-range-to-c.pa
tch

  MergePinUnpin doesn't need to load the whole table into
memory at once, it's 
enough to hold a timestamp-limited range of records.

0006-Do-not-fetch-the-table-into-memory-in-BuildComments.pat
ch

  BuildComments doesn't need to load the table at all, it's
better to keep a 
list of records to update afterwards. Also fixes a bug in
newline handling.

0007-Added-options-to-prune-orphaned-files-and-labels-fro.pa
tch

  Most of orphans in that repository come from unneeded
projects removed 
before conversion. This patch adds an option to
automatically remove all 
orphans, except for the ones absolutely necessary for
correct conversion. 
Doing it on the stage of computing the set of actions
guarantees a valid dump 
file.

  Without removing orphans, SVN consumes about 200KB per
revision (apparently, 
it cannot diff directories, and the /orphaned dir gets very
large).

0008-Fixed-a-problem-in-chain-share-handling.patch

  In some cases, when a file is shared into a path,
branched, then immediately 
reshared to another path, etc, vss2svn generates a command
to copy from the 
current revision, and svnadmin doesn't like that. This quick
fix avoids the 
problem by beginning a new revision on shares from a path,
that was touched 
by the current revision.

0009-Fixed-a-bug-in-handling-restore-with-labels.patch

  Fixes a bug in the recent patch, which produces invalid
paths if the last 
action in a restored project was adding a label.

  I'm not sure about this bit, I just thought it strange
that we should 
completely reset the version numbers, even if they are
available:

 -474,13
+474,18  sub _restore_handler {
          type       => $row->,
          name       => $row->,
          parents    => {},
-         first_version => 1,
-         last_version => 1,
+         first_version => $gPhysInfo{
$row-> } || 1,
+         last_version => $gPhysInfo{ $row->
} || 1,
          orphaned   => 1,
          was_binary => $row->,
     };

0010-Recover-files-with-corrupted-history-at-branch-point.pa
tch

  In the trunk version, if a physical file is lost, all
files, branched from 
it, are not converted, despite the fact that all versions
after the branch 
are available. This patch adds a check to re-add such files
at the branch 
point.

0011-Support-rolling-back-during-branching.patch

  Branching CAN be combined with rollback, so it's not
always a no-op in SVN. 
This patch introduces a new ROLLBACK action to handle that
case.


P.S. Is it by design that Subversion stores all 110000
revisions in one 
directory?

Alexander

_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.
pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/lis
tinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-c
ontrol.subversion.vss2svn.user

Alexander N. Gavrilov wrote :
> Subject: More patches for vss2svn

Alexander,
Your patches sound very useful and I hope they can be
integrated into
the trunk to help future users.

I just thought I'd reply to this question :
 
> P.S. Is it by design that Subversion stores all 110000
revisions in
one
> directory?

This has long been recognized a potential source of concern
(though in
fact, benchmarks tend to show it is not a problem for most
UNIX
filesystems) in the FSFS backend, and it is being addressed
in
Subversion 1.5 :
http://subversion.tigris.org/svn_1.5_release
notes.html#fsfs-sharding

Cheers,
--Jonathan

_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.
pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/lis
tinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-c
ontrol.subversion.vss2svn.user

On Thursday 29 May 2008 03:23:27 Toby Johnson wrote:
> Thanks for all the hard work you've put into your
patches! I wish I
> would have known ahead of time that you would be
submitting so many, I
> could have given you commit access on your own branch
to make managing
> and reviewing them easier. In fact I will still
probably create a branch
> for these just so I can keep track while I commit them.
I'll reply back
> once I've got them committed and hopefully others can
help with
> reviewing/testing.

Hello,

Well, I didn't know that myself. I just tweaked one thing,
then another, and 
so on.  =)

Actually, this conversion was some sort of a feasibility
study. If the big 
bosses agree to do an actual switch, I'll be converting
everything afresh, 
probably with a slightly different set of projects; besides,
there is a 
completely separate repository of the QA group, undoubtely
with it's own 
quirks. In that case I might have to do some more changes,
and committing 
them directly to a separate branch would indeed be more
convenient. However, 
I don't expect that to be very soon.

In the meanwhile, after some hacking on git-svnimport I also
succeeded in 
further converting the repository to Git, and during this
weekend wrote a 
script for bidirectional exchange of simple changes between
Git and VSS, 
using VSS's logging facility. It's still full of bugs,
though...

Alexander.

_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.
pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/lis
tinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-c
ontrol.subversion.vss2svn.user