You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Vincent QB <vi...@gmail.com> on 2013/11/02 08:06:32 UTC
Corrupted Repository
Hello,
0. I've updated to Ubuntu 13.10 recently. I'm using btrfs since about
August.
1. Very recently, my repository (~90gb) started giving an error when I
update my checked out copy:
svn: E160004: Corrupt node-revision '3-2320.0-1861.r2320/7091583216'
svn: E160004: Found malformed header
'g?\229?\143#?\239?\140?\224s?\146G^?\166?\183?\169M-?\206?\168?\165/?\244?\216ncIY?\237?\222?\228K?\231?\192"?\181Q?\180?\131?\128
'?\235?\200?\250z?\214F?\1665?\137o#?\131S?\154?\23963I*?\172?\215r?\186E&63''
in revision file
2. When doing svn status, I see four folders with an ! next to them. I can
svn update the others, but not those.
3. svn verify fails with error:
svnadmin: E160004: Revision file (r776) lacks trailing newline
4. When trying to rebuild a copy of my repositories using old backup dump
files, the process stops with the error
svnadmin: E185003: Invalid diff stream: insn 0 overflows the target view
Strangely enough, this repository was most likely a rebuilt of the same
dump files, and so the process of rebuilding from those dump worked at some
point in time, before updating.
5. My svnsync'ed copy on a much older remote computer runs svn verify
without errors. [I will not be able to transfer large files from that
remote computer.] However, I've discovered that all revisions since around
August (around revision 4000 and up) on that backup have the exact same
size of a few bytes. I suspect this is an independent problem though.
What is the recommended course of action to recover a fully functional
repository? Thank you!
Re: Corrupted Repository
Posted by Vincent Quenneville-Belair <vq...@umn.edu>.
For the record, the problem was the following. Fixed.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243636
On Sun, Nov 3, 2013 at 12:30 PM, Vincent Quenneville-Belair <vq...@umn.edu> wrote:
> Sorry I just made a mistake. When I copied the repository inside the
> ubuntu home encryption with Ubuntu 13.10, I started having the same
> problems as before...
>
> On Sun, Nov 3, 2013 at 12:27 PM, Vincent Quenneville-Belair <vq...@umn.edu> wrote:
>> When booting in Ubuntu 13.04 through a USB key, I was able to mount
>> the encrypted home folder in read only, and then dump, load, and
>> verify outside of the encrypted home in 13.04 (but still on btrfs).
>> Moreover, when I returned to 13.10, I was able to "svn verify" the
>> repository outside of the encrypted home.
>>
>> And what's more is that I was able to make a copy of that new
>> repository inside the encrypted home, and "svn verify" it using Ubuntu
>> 13.10. Something must have gone wrong with ubuntu home encryption
>> 13.10 and some files in the repository.
>>
>> Anyway, as I recovered my repository, I'm happy now.
>>
>> On Sun, Nov 3, 2013 at 1:05 AM, Vincent Quenneville-Belair <vq...@umn.edu> wrote:
>>> Good evening!
>>>
>>> I don't think it's btrfs.
>>> -- I'm using btrfs since August, but the problem came up only
>>> recently, after installing Ubuntu 13.10.
>>> -- I loaded the repository in an ext4 partition from a dump made
>>> before using btrfs, with the same result.
>>> -- I booted Ubuntu 13.04 through a USB key, and I successfully dumped,
>>> loaded, and verified the repository.
>>>
>>> Any other ideas? Thank you!
>>>
>>> On Nov 2, 2013 6:17 PM, "Thorsten Schöning" <ts...@am-soft.de> wrote:
>>>>
>>>> Guten Tag Vincent QB,
>>>> am Samstag, 2. November 2013 um 23:15 schrieben Sie:
>>>>
>>>> > The problems appear starting with the version of subversion in
>>>> > Ubuntu 13.10 (version 1.7.9 along with 1.8.4). If I go back to
>>>> > Ubuntu 13.04 (version 1.7.5), the problems disappear. I was able to
>>>> > create a new dump. However, it crashes in the same way when loading in Ubuntu 13.10.
>>>>
>>>> From your former mail:
>>>>
>>>> > [...]I'm using btrfs since about August.
>>>>
>>>> > [...]However, I've discovered that all
>>>> > revisions since around August (around revision 4000 and up) on that
>>>> > backup have the exact same size of a few bytes.
>>>>
>>>> Did you use BTRFS in 13.04 as well? I wonder if your problem has
>>>> simply nothing to do with Subversion, but with the usage of a still
>>>> experimental file system, which is not meant to be in production use.
>>>>
>>>> Mit freundlichen Grüßen,
>>>>
>>>> Thorsten Schöning
>>>>
>>>> --
>>>> Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
>>>> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>>>>
>>>> Telefon...........05151- 9468- 55
>>>> Fax...............05151- 9468- 88
>>>> Mobil..............0178-8 9468- 04
>>>>
>>>> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
>>>> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>>>>
Re: Corrupted Repository
Posted by Vincent Quenneville-Belair <vq...@umn.edu>.
Sorry I just made a mistake. When I copied the repository inside the
ubuntu home encryption with Ubuntu 13.10, I started having the same
problems as before...
On Sun, Nov 3, 2013 at 12:27 PM, Vincent Quenneville-Belair <vq...@umn.edu> wrote:
> When booting in Ubuntu 13.04 through a USB key, I was able to mount
> the encrypted home folder in read only, and then dump, load, and
> verify outside of the encrypted home in 13.04 (but still on btrfs).
> Moreover, when I returned to 13.10, I was able to "svn verify" the
> repository outside of the encrypted home.
>
> And what's more is that I was able to make a copy of that new
> repository inside the encrypted home, and "svn verify" it using Ubuntu
> 13.10. Something must have gone wrong with ubuntu home encryption
> 13.10 and some files in the repository.
>
> Anyway, as I recovered my repository, I'm happy now.
>
> On Sun, Nov 3, 2013 at 1:05 AM, Vincent Quenneville-Belair <vq...@umn.edu> wrote:
>> Good evening!
>>
>> I don't think it's btrfs.
>> -- I'm using btrfs since August, but the problem came up only
>> recently, after installing Ubuntu 13.10.
>> -- I loaded the repository in an ext4 partition from a dump made
>> before using btrfs, with the same result.
>> -- I booted Ubuntu 13.04 through a USB key, and I successfully dumped,
>> loaded, and verified the repository.
>>
>> Any other ideas? Thank you!
>>
>> On Nov 2, 2013 6:17 PM, "Thorsten Schöning" <ts...@am-soft.de> wrote:
>>>
>>> Guten Tag Vincent QB,
>>> am Samstag, 2. November 2013 um 23:15 schrieben Sie:
>>>
>>> > The problems appear starting with the version of subversion in
>>> > Ubuntu 13.10 (version 1.7.9 along with 1.8.4). If I go back to
>>> > Ubuntu 13.04 (version 1.7.5), the problems disappear. I was able to
>>> > create a new dump. However, it crashes in the same way when loading in Ubuntu 13.10.
>>>
>>> From your former mail:
>>>
>>> > [...]I'm using btrfs since about August.
>>>
>>> > [...]However, I've discovered that all
>>> > revisions since around August (around revision 4000 and up) on that
>>> > backup have the exact same size of a few bytes.
>>>
>>> Did you use BTRFS in 13.04 as well? I wonder if your problem has
>>> simply nothing to do with Subversion, but with the usage of a still
>>> experimental file system, which is not meant to be in production use.
>>>
>>> Mit freundlichen Grüßen,
>>>
>>> Thorsten Schöning
>>>
>>> --
>>> Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
>>> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>>>
>>> Telefon...........05151- 9468- 55
>>> Fax...............05151- 9468- 88
>>> Mobil..............0178-8 9468- 04
>>>
>>> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
>>> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>>>
Re: Corrupted Repository
Posted by Vincent Quenneville-Belair <vq...@umn.edu>.
When booting in Ubuntu 13.04 through a USB key, I was able to mount
the encrypted home folder in read only, and then dump, load, and
verify outside of the encrypted home in 13.04 (but still on btrfs).
Moreover, when I returned to 13.10, I was able to "svn verify" the
repository outside of the encrypted home.
And what's more is that I was able to make a copy of that new
repository inside the encrypted home, and "svn verify" it using Ubuntu
13.10. Something must have gone wrong with ubuntu home encryption
13.10 and some files in the repository.
Anyway, as I recovered my repository, I'm happy now.
On Sun, Nov 3, 2013 at 1:05 AM, Vincent Quenneville-Belair <vq...@umn.edu> wrote:
> Good evening!
>
> I don't think it's btrfs.
> -- I'm using btrfs since August, but the problem came up only
> recently, after installing Ubuntu 13.10.
> -- I loaded the repository in an ext4 partition from a dump made
> before using btrfs, with the same result.
> -- I booted Ubuntu 13.04 through a USB key, and I successfully dumped,
> loaded, and verified the repository.
>
> Any other ideas? Thank you!
>
> On Nov 2, 2013 6:17 PM, "Thorsten Schöning" <ts...@am-soft.de> wrote:
>>
>> Guten Tag Vincent QB,
>> am Samstag, 2. November 2013 um 23:15 schrieben Sie:
>>
>> > The problems appear starting with the version of subversion in
>> > Ubuntu 13.10 (version 1.7.9 along with 1.8.4). If I go back to
>> > Ubuntu 13.04 (version 1.7.5), the problems disappear. I was able to
>> > create a new dump. However, it crashes in the same way when loading in Ubuntu 13.10.
>>
>> From your former mail:
>>
>> > [...]I'm using btrfs since about August.
>>
>> > [...]However, I've discovered that all
>> > revisions since around August (around revision 4000 and up) on that
>> > backup have the exact same size of a few bytes.
>>
>> Did you use BTRFS in 13.04 as well? I wonder if your problem has
>> simply nothing to do with Subversion, but with the usage of a still
>> experimental file system, which is not meant to be in production use.
>>
>> Mit freundlichen Grüßen,
>>
>> Thorsten Schöning
>>
>> --
>> Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
>> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>>
>> Telefon...........05151- 9468- 55
>> Fax...............05151- 9468- 88
>> Mobil..............0178-8 9468- 04
>>
>> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
>> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>>
Re: Corrupted Repository
Posted by Vincent Quenneville-Belair <vq...@umn.edu>.
Good evening!
I don't think it's btrfs.
-- I'm using btrfs since August, but the problem came up only
recently, after installing Ubuntu 13.10.
-- I loaded the repository in an ext4 partition from a dump made
before using btrfs, with the same result.
-- I booted Ubuntu 13.04 through a USB key, and I successfully dumped,
loaded, and verified the repository.
Any other ideas? Thank you!
On Nov 2, 2013 6:17 PM, "Thorsten Schöning" <ts...@am-soft.de> wrote:
>
> Guten Tag Vincent QB,
> am Samstag, 2. November 2013 um 23:15 schrieben Sie:
>
> > The problems appear starting with the version of subversion in
> > Ubuntu 13.10 (version 1.7.9 along with 1.8.4). If I go back to
> > Ubuntu 13.04 (version 1.7.5), the problems disappear. I was able to
> > create a new dump. However, it crashes in the same way when loading in Ubuntu 13.10.
>
> From your former mail:
>
> > [...]I'm using btrfs since about August.
>
> > [...]However, I've discovered that all
> > revisions since around August (around revision 4000 and up) on that
> > backup have the exact same size of a few bytes.
>
> Did you use BTRFS in 13.04 as well? I wonder if your problem has
> simply nothing to do with Subversion, but with the usage of a still
> experimental file system, which is not meant to be in production use.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>
> Telefon...........05151- 9468- 55
> Fax...............05151- 9468- 88
> Mobil..............0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
Re: Corrupted Repository
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Vincent QB,
am Samstag, 2. November 2013 um 23:15 schrieben Sie:
> The problems appear starting with the version of subversion in
> Ubuntu 13.10 (version 1.7.9 along with 1.8.4). If I go back to
> Ubuntu 13.04 (version 1.7.5), the problems disappear. I was able to
> create a new dump. However, it crashes in the same way when loading in Ubuntu 13.10.
From your former mail:
> [...]I'm using btrfs since about August.
> [...]However, I've discovered that all
> revisions since around August (around revision 4000 and up) on that
> backup have the exact same size of a few bytes.
Did you use BTRFS in 13.04 as well? I wonder if your problem has
simply nothing to do with Subversion, but with the usage of a still
experimental file system, which is not meant to be in production use.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Corrupted Repository
Posted by Vincent QB <vi...@gmail.com>.
Hello again,
The problems appear starting with the version of subversion in Ubuntu 13.10
(version 1.7.9 along with 1.8.4). If I go back to Ubuntu 13.04 (version
1.7.5), the problems disappear. I was able to create a new dump. However,
it crashes in the same way when loading in Ubuntu 13.10.
Could this be a bug in the more recent versions?
On Sat, Nov 2, 2013 at 2:06 AM, Vincent QB <vi...@gmail.com> wrote:
> Hello,
>
> 0. I've updated to Ubuntu 13.10 recently. I'm using btrfs since about
> August.
>
> 1. Very recently, my repository (~90gb) started giving an error when I
> update my checked out copy:
> svn: E160004: Corrupt node-revision '3-2320.0-1861.r2320/7091583216'
> svn: E160004: Found malformed header
> 'g?\229?\143#?\239?\140?\224s?\146G^?\166?\183?\169M-?\206?\168?\165
> /?\244?\216ncIY?\237?\222?\228K?\231?\192"?\181Q?\180?\131?\128 '?\235?\200?\250z?\214F?\1665?\137o#?\131S?\154?\23963I*?\172?\215r?\186E&63''
> in revision file
>
> 2. When doing svn status, I see four folders with an ! next to them. I can
> svn update the others, but not those.
>
> 3. svn verify fails with error:
> svnadmin: E160004: Revision file (r776) lacks trailing newline
>
> 4. When trying to rebuild a copy of my repositories using old backup dump
> files, the process stops with the error
> svnadmin: E185003: Invalid diff stream: insn 0 overflows the target view
> Strangely enough, this repository was most likely a rebuilt of the same
> dump files, and so the process of rebuilding from those dump worked at some
> point in time, before updating.
>
> 5. My svnsync'ed copy on a much older remote computer runs svn verify
> without errors. [I will not be able to transfer large files from that
> remote computer.] However, I've discovered that all revisions since around
> August (around revision 4000 and up) on that backup have the exact same
> size of a few bytes. I suspect this is an independent problem though.
>
> What is the recommended course of action to recover a fully functional
> repository? Thank you!
>