Thanks for the response. It sounds like it would be better to move
the corrupt repos to another *nix (instead of windows).
My new plan is to move the corrupt SVN 1.4.0 repos (on the FreeBSD 6.1-
RELEASE machine)via TAR + NFS to a Red Hat Linux 5.3 box (with SVN
1.4.0).
If I can get them there an
om
scratch with all new repos). My goal is to just move these old repos
to the destination server by whatever means possible (and as of right
now... the aforementioned commands aren't working).
thank you so much!
On May 13, 2:41 am, Ryan Schmidt
wrote:
> On May 13, 2010, at 02:35, St
I need to move a few very large repositories (one over 30 GB) to
another server (both servers use SVN 1.4.0.)
Server 1: FreeBSD 6.0
Server 2: Windows Server 2003 x64
Transfer method: NFS (Network File Share)
Are there any issues with just tarring up the repositories and
transferring them over NFS
.
svnsync: REPORT request failed on 'https://'
svnsync: REPORT of 'https://': 200 OK (https://)
On Apr 13, 1:05 pm, Stonebraker wrote:
> Any update on this? Did svnsync fix your issue?
>
> I am receiving the same error when trying to dump a 46 gb repo
> *
Any update on this? Did svnsync fix your issue?
I am receiving the same error when trying to dump a 46 gb repo
* Dumped revision 1703.
* Dumped revision 1704.
* Dumped revision 1705.
svnadmin: Malformed representation header
svnhotcopy only copies about 6gb of the repo!
(I am using version 1.4.
