[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: HELP: Upgraded to v 1.4.5 and now have a "Found malformed header in revision file" error

From: <david.x.grierson_at_jpmorgan.com>
Date: Wed, 30 Jan 2008 16:31:07 +0000

Been doing a bit of looking around for the root cause ... could this be
caused by the worker MPM being used with mod_dav_svn rather than prefork?

I can't find any references to this not being an appropriate configuration
other than this thread back in 2002:

http://svn.haxx.se/dev/archive-2002-11/0391.shtml

Is anyone else running the worker MPM without any issues or should I
switch it to the prefork MPM?

Thanks again guys,

Dg.

--
David Grierson
JPMorgan - IB Architecture - Source Code Management Consultant
GDP 228-5574 / DDI +44 141 228 5574 / Email david.x.grierson_at_jpmorgan.com
Alhambra House 6th floor, 45 Waterloo Street, Glasgow G2 6HS
 
 IB Architecture - AD Tools - Tel 8 228 5574
David X Grierson/JPMCHASE
30/01/2008 14:33
To
"Paul Koning" <Gerard_Koning_at_Dell.com>
cc
users_at_subversion.tigris.org
Subject
RE:  HELP: Upgraded to v 1.4.5 and now have a "Found malformed header in 
revision file" error
Firstly apologies for the formatting of this email and the top posting - I 
have to use Lotus Notes which really doesn't lend itself to Internet 
email.
Thanks for the suggestion ... I've copied the whole repository over to a 
host running the old 1.3.2 environment to attempt the dump there - the 
dump fails on revision with the "Found malformed header ..." message.
Regards,
David.
--
David Grierson
JPMorgan - IB Architecture - Source Code Management Consultant
GDP 228-5574 / DDI +44 141 228 5574 / Email david.x.grierson_at_jpmorgan.com
Alhambra House 6th floor, 45 Waterloo Street, Glasgow G2 6HS
 
"Paul Koning" <Gerard_Koning_at_Dell.com> 
30/01/2008 13:41
To
<david.x.grierson_at_jpmorgan.com>, <users_at_subversion.tigris.org>
cc
Subject
RE:  HELP: Upgraded to v 1.4.5 and now have a "Found malformed header in 
revision file" error
Something you might try: install the older version again, svndump the
repository, install the new version, rename your existing repository,
svnload from the dump to recreate the repository.
The dump->load procedure may cure whatever was wrong.
                 paul
> -----Original Message-----
> From: david.x.grierson_at_jpmorgan.com 
> [mailto:david.x.grierson_at_jpmorgan.com] 
> Sent: Wednesday, January 30, 2008 7:06 AM
> To: users_at_subversion.tigris.org
> Subject: HELP: Upgraded to v 1.4.5 and now have a "Found 
> malformed header in revision file" error
> Importance: High
> 
> 
> Hi,
> We recently migrated to a 1.4.5 environment and have just 
> experiencing the 
> "Found malformed header in revision file" error on one of our 
> repositories.
> Can someone please help - there doesn't appear to be any way 
> in which to 
> recover from this.
> Can I remove the revision and it's properties or will I have 
> to recover 
> from tape?
> $ svnlook changed -r22869 /svnstorage/svn1/repos/neoallcli
> svnlook: Found malformed header in revision file
> $ svnlook log -r22869 /svnstorage/svn1/repos/neoallcli
> NEO-2078 NEO PLUGIN REFACTORING
> $ cd /svnstorage/svn1/repos/neoallcli/db/revs
> $ ls -l 22869
> -rw-r--r--  1 a_svn adtools 3241577 Jan 30 11:22 22869
> 
> Many thanks in advance,
> David.
> --
> David Grierson
> JPMorgan - IB Architecture - Source Code Management Consultant
> GDP 228-5574 / DDI +44 141 228 5574 / Email 
> david.x.grierson_at_jpmorgan.com
> Alhambra House 6th floor, 45 Waterloo Street, Glasgow G2 6HS
> 
> Generally, this communication is for informational purposes only
> and it is not intended as an offer or solicitation for the purchase
> or sale of any financial instrument or as an official confirmation
> of any transaction. In the event you are receiving the offering
> materials attached below related to your interest in hedge funds or
> private equity, this communication may be intended as an offer or
> solicitation for the purchase or sale of such fund(s).  All market
> prices, data and other information are not warranted as to
> completeness or accuracy and are subject to change without notice.
> Any comments or statements made herein do not necessarily reflect
> those of JPMorgan Chase & Co., its subsidiaries and affiliates.
> 
> This transmission may contain information that is privileged,
> confidential, legally privileged, and/or exempt from disclosure
> under applicable law. If you are not the intended recipient, you
> are hereby notified that any disclosure, copying, distribution, or
> use of the information contained herein (including any reliance
> thereon) is STRICTLY PROHIBITED. Although this transmission and any
> attachments are believed to be free of any virus or other defect
> that might affect any computer system into which it is received and
> opened, it is the responsibility of the recipient to ensure that it
> is virus free and no responsibility is accepted by JPMorgan Chase &
> Co., its subsidiaries and affiliates, as applicable, for any loss
> or damage arising in any way from its use. If you received this
> transmission in error, please immediately contact the sender and
> destroy the material in its entirety, whether in electronic or hard
> copy format. Thank you.
> Please refer to http://www.jpmorgan.com/pages/disclosures for
> disclosures relating to UK legal entities.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
> 
> 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-30 17:32:10 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.