Re: How to recover from "Found malformed header in revision file"?
Steven Roussey
>
> How to recover from "Found malformed header in revision file"?
>
> > svn commit myfile
> Sending myfile
> Transmitting file data .svn: Commit failed (details follow):
> svn: Corrupt node-revision '0-484.0-123.r993/92'
> svn: Found malformed header in revision file
>
> So I tried create a dump file:
> > svnadmin dump /site/svn/ > dumpsvn
> * Dumped revision 0.
> ...
> * Dumped revision 987.
> svnadmin: Corrupt representation '988 0 8767 8749
> 17d4a0cc3e480c0c64dd8107a1854b7f'
> svnadmin: Malformed representation header
>
> So it started a long long time ago... :(
>
> > svn --version
> svn, version 1.5.1 (r32289)
> compiled Aug 7 2009, 01:15:13
>
> This the version of svn from ubuntu for whatever version is running on
> that machine.
>
> If a dump of the repo doesn't work, what next???
>
>
I also tried svnadmin recover which did not work, and fsfsverify.py. I have a
few working copies around that are ok (I think) -- is there a way to use that to
fix the repository?
Steven Roussey
Network54 Corp.
Mariusz Droździel
> I also tried svnadmin recover which did not work, and fsfsverify.py. I have a
> few working copies around that are ok (I think) -- is there a way to use that to
> fix the repository?
Check out "Corrupted FSFS commit" and "Broken Revision in FSFS Repo"
threads from few days ago. I think me and Martin had very similiar
problem and solved it out with svnsync + access control over webdav.
--
Mariusz Drozdziel
Steven Roussey
and create a new repo. Anyhow, the svnsync idea is a good one, and
I'll have to give that a try. Thanks!
Steven Roussey
Network54 Corp.
2010/3/3 Mariusz Droździel <mdroz...@gmail.com>:
Stonebraker
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.0 (r21228))
Any ideas? I was thinking about trying svnsync but there is a bug in
that version where i cannot do svnsync over https without accepting
the certificate every time.
On Mar 8, 12:25 pm, Steven Roussey <srous...@network54.com> wrote:
> I can do a full checkout at the moment. Too bad I can't go from that
> and create a new repo. Anyhow, the svnsync idea is a good one, and
> I'll have to give that a try. Thanks!
>
> Steven Roussey
> Network54 Corp.
>
> 2010/3/3 Mariusz Droździel <mdrozdz...@gmail.com>:
Stonebraker
when attempting to dump my repo. Svnsync fails after eight revisions
(SVN version 1.4.0 (r21228))
Console output:
...
Committed revision 8.
Copied properties for revision 8.
Committed revision 9.
Copied properties for revision 9.
svnsync: REPORT request failed on 'https://<url removed>'
svnsync: REPORT of 'https://<url removed>': 200 OK (https://<url
removed>)
On Apr 13, 1:05 pm, Stonebraker <steve.stonebra...@gmail.com> wrote:
> 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.0 (r21228))
>
> Any ideas? I was thinking about trying svnsync but there is a bug in
> that version where i cannot do svnsync over https without accepting
> the certificate every time.
>
> On Mar 8, 12:25 pm, Steven Roussey <srous...@network54.com> wrote:
>
> > I can do a full checkout at the moment. Too bad I can't go from that
> > and create a new repo. Anyhow, the svnsync idea is a good one, and
> > I'll have to give that a try. Thanks!
>
> > Steven Roussey
> > Network54 Corp.
>
> > 2010/3/3 Mariusz Dro¼dziel <mdrozdz...@gmail.com>: