Johan,
>> - Is it safe to use svnadmin dump on the source repository? As in
>> does it do it change in the source repo?
>
> Yes, it's absolutely safe to run on the source repository, it should
> not cause anything to change in the source repo.
Thanks. What about "svnadmin verify /var/svn/projects" ?
>
>> - What causes E200015? I don't think its permission as I have even
>> attempted to run svnadmin dump with root permissions? How can I
>> overcome the issue?
>
> Is that the full error message you gave?
Yes, that was it. There was nothing else that it threw at standard
error during the dump
>
> "Caught signal" would be what you'd get if the process were aborted by
> a signal, like aborting it with Ctrl-C, or if some other user with
> enough permissions sends a kill signal to your process or something
> like that.
>
> Is it always aborting at the same revision?
Yes, actually think its corruption related. I did manage dumping the
repo in full but have not been able to restore it. The restore fails
with the same error.
* editing path :
condor/trunk/work/design/ic/library/kl_condor/kl_vco_curmir_1to20mA/starrc/layout.oa
... done.
svnadmin: E200015: Caught signal
<<< Started new transaction, based on original revision 7001
* editing path :
condor/trunk/work/design/ic/library/yt_tmp/DM10_B_DUM ...svnadmin:
E160013: File not found: transaction '6490-50b', path
'/condor/trunk/work/design/ic/library/yt_tmp/DM10_B_DUM'
Note, its attempting to restore revision 7001 but the previous
revision is 6491. So, the file don't exist because it was created in
the future
>
> Maybe someone else is interfering with your work, and (accidently)
> killing your process? Or maybe your remote (ssh / whatever) session
> gets disconnected which causes the dump process to abort?
No, petty sure, I am the only one who have access to the new SVN
server but have seem E200015 error as seem above
>
> --
> Johan
Thanks a lot Johan
Regards,
William
