You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by da...@jpmorgan.com on 2008/01/30 12:06:19 UTC
HELP: Upgraded to v 1.4.5 and now have a "Found malformed header in
revision file" error
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@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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: HELP: Upgraded to v 1.4.5 and now have a "Found malformed header
in revision file" error
Posted by Pekka Niiranen <pe...@pp5.inet.fi>.
david.x.grierson@jpmorgan.com wrote:
> 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@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.
I had similar problems after v1.4.3 => v1.4.5 upgrade.
Sometimes md-sums where identical between same files
(I replaced them manually to zeros.) and sometimes letters
in path names had changed. Also revisions years ago became
suddently corrupted and no one could "svn update" anymore.
I had to fix them by editing revision records manually
with VI -editor. I also used python script to analyse problems
and had to add extra printf -clauses to Subversion C-source files
in order to locate errors.
I have upgraded the server to v1.4.6 and "svnadmin verify" has not
reported any problems since then. I am using FSFS.
-pekka-
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: HELP: Upgraded to v 1.4.5 and now have a "Found malformed header
in revision file" error
Posted by Pekka Niiranen <pe...@pp5.inet.fi>.
david.x.grierson@jpmorgan.com wrote:
> 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@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.
I had similar problems after v1.4.3 => v1.4.5 upgrade.
Sometimes md-sums where identical between same files
(I replaced them manually to zeros.) and sometimes letters
in path names had changed. Also revisions years ago became
suddently corrupted and no one could "svn update" anymore.
I had to fix them by editing revision records manually
with VI -editor. I also used python script to analyse problems
and had to add extra printf -clauses to Subversion C-source files
in order to locate errors.
I have upgraded the server to v1.4.6 and "svnadmin verify" has not
reported any problems since then. I am using FSFS.
-pekka-
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re:
RE: HELP: Upgraded to v 1.4.5 and now have a "Found malformed header in
revision file" error
Posted by Paul Koning <pk...@equallogic.com>.
>>>>> "david" == david x grierson <da...@jpmorgan.com> writes:
david> Thanks for the suggestion ... I've copied the whole repository
david> over to a host running the old 1.3.2 environment to attempt
david> the dump there - the dump fails on revision with the "Found
david> malformed header ..." message.
Unfortunately that leaves me out of ideas. It sounds like the
repository was corrupted some time ago, and the error wasn't spotted
because nothing people were doing back then was running into the
issue. That happened to us once -- very strange -- it wasn't the
message you mentioned, though.
If you can identify the rev that has the issue (it should be clear
from the messages printed during the dump -- it prints each rev number
as it dumps it, right?) you could try doing a two-part dump. If the
bad rev is rev N, dump revs 1:N-1 then N+1:HEAD, and load those.
You'll lose one rev. If anyone has a working directory you will
hopefully be able to reconstruct the missing rev.
Alternatively, it might be possible to look in the repository innards
to examine the rev file with the error, to see if it can be patched.
I haven't had to do that so I don't have any idea whether there is any
chance of that working...
paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: HELP: Upgraded to v 1.4.5 and now have a "Found malformed header in
revision file" error
Posted by da...@jpmorgan.com.
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@jpmorgan.com
Alhambra House 6th floor, 45 Waterloo Street, Glasgow G2 6HS
"Paul Koning" <Ge...@Dell.com>
30/01/2008 13:41
To
<da...@jpmorgan.com>, <us...@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@jpmorgan.com
> [mailto:david.x.grierson@jpmorgan.com]
> Sent: Wednesday, January 30, 2008 7:06 AM
> To: users@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@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@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: HELP: Upgraded to v 1.4.5 and now have a "Found malformed header in revision file" error
Posted by Paul Koning <Ge...@Dell.com>.
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@jpmorgan.com
> [mailto:david.x.grierson@jpmorgan.com]
> Sent: Wednesday, January 30, 2008 7:06 AM
> To: users@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@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@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org