You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Dirk Taggesell <di...@proximic.com> on 2009/06/25 15:38:34 UTC
corrupted fsfs repository, tools for repair?
Dear subversion users,
today I ran in a problem with my repository. The server is
Mac OS X 10.4, subversion and apache are from the macports,
the repository is accessed via apache and mod_dav_svn v. 1.4.0
The repository stores data as FSFS.
There has been an undetected filesystem error on the volume
with the repository, corrupting it.
Now if I want to check out, I receive errors like this:
"svn: REPORT of '/svn/repo/!svn/vcc/default': Could not read
chunk delimiter: Secure connection truncated"
I copied the repository over to my Mac and tried to repair it
using the current macports subversion 1.6.3.
First I inspected the repository and "svnadmin verify" tells me:
--- snip ---
* Verified revision 0.
* Verified revision 1.
* Verified revision 2.
* Verified revision 3.
* Verified revision 4.
* Verified revision 5.
* Verified revision 6.
svnadmin: Invalid diff stream: insn 2403 cannot be decoded
--- snap ---
A svnadmin recover seems to find nothing:
--- snip ---
Repository lock acquired.
Please wait; recovering the repository may take some time...
Recovery completed.
The latest repos revision is 17985.
--- snap ---
But it appears that it actually repairs nothing. As far as
I've read the recover command is mainly for repositories using
Berkeley db.
Anyway, I then downloaded Mr. Zakmeisters fsfsverify, but I'm
not entirely sure how to use it properly.
So svnadmin verify stops at revision 6 and complains about
"insn 2403". Does that mean that revision 7 is corrupt and i
should run "fsfsverify.py -f svn/repo/db/revs/7"?
After doing this, fsfsverify tells me: "Fixed? :-) Re-run
fsfsverify without the -f option" and once I do this, it gives
me an "Error InvalidWindow: ..." all the time, after each repair
run with a different number.
Does this mean, I simply have to run it again and again until the
error is gone? Or is the tool at its wit's end? And the repository
corrupted beyond repair?
Is there anything else (other than restore from the backup) I can do to
recover the repository?
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2365616
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: corrupted fsfs repository, tools for repair?
Posted by Dirk Taggesell <di...@proximic.com>.
John Szakmeister wrote:
> That's a bummer. Sounds like there was something more seriously
> corrupted there.
Not overly surprising, as the filesystem was definitely corrupted and
then subversion cannot do much to prevent corrupting the repository as well.
Mac OS told me it repaired something as I ran a filesystem repair.
Unfortunately files had to be deleted as they were beyond repair. The
entire issue came up when my nightly svn backup was crapping out with
strange errors, which it sent to me by mail, luckily. Else the
corruption could have ensued for weeks undetected ....
Am considering to host the svn on a solaris with zfs. Silently corrupted
filesystems aren't possible there.
--
kind regards
Dirk Taggesell
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2366711
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: corrupted fsfs repository, tools for repair?
Posted by John Szakmeister <jo...@szakmeister.net>.
On Tue, Jun 30, 2009 at 6:50 AM, Dirk Taggesell
<di...@proximic.com> wrote:
>
> John Szakmeister wrote:
>
> > You did back up the rev like the huge warning told you, right?
>
> Sure, was working on the copy anyway.
Great.
> > Your rev can be corrupt in more than one location. fsfsverify only
> > fixes the first one that it finds. The fact that the number is
> > changing is actually a good thing. It likely means you have several
> > repeated blocks.
> [...]
> > I've seen both sides. I have had to run the tool as much as 9 times
> > on some revisions because there were that many repeated blocks.
>
> I ran it about a hundred times on the particular revision until it gave up.
>
> So the repository couldn't be repaired, I lost interest and restored the
> most recent backup that validated. Two day's history lost, no loss of
> work at all as I still had my local files.
That's a bummer. Sounds like there was something more seriously
corrupted there.
> Anyway: Thanks for any help!
You're welcome!
-John
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2366676
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: corrupted fsfs repository, tools for repair?
Posted by Dirk Taggesell <di...@proximic.com>.
John Szakmeister wrote:
> You did back up the rev like the huge warning told you, right?
Sure, was working on the copy anyway.
> Your rev can be corrupt in more than one location. fsfsverify only
> fixes the first one that it finds. The fact that the number is
> changing is actually a good thing. It likely means you have several
> repeated blocks.
[...]
> I've seen both sides. I have had to run the tool as much as 9 times
> on some revisions because there were that many repeated blocks.
I ran it about a hundred times on the particular revision until it gave up.
So the repository couldn't be repaired, I lost interest and restored the
most recent backup that validated. Two day's history lost, no loss of
work at all as I still had my local files.
Anyway: Thanks for any help!
--
kind regards
Dirk Taggesell
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2366662
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: corrupted fsfs repository, tools for repair?
Posted by John Szakmeister <jo...@szakmeister.net>.
On Thu, Jun 25, 2009 at 11:38 AM, Dirk Taggesell
<di...@proximic.com> wrote:
[snip]
> A svnadmin recover seems to find nothing:
> --- snip ---
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> The latest repos revision is 17985.
> --- snap ---
>
> But it appears that it actually repairs nothing. As far as
> I've read the recover command is mainly for repositories using
> Berkeley db.
Correct. It doesn't do anything for fsfs.
> Anyway, I then downloaded Mr. Zakmeisters fsfsverify, but I'm
> not entirely sure how to use it properly.
>
> So svnadmin verify stops at revision 6 and complains about
> "insn 2403". Does that mean that revision 7 is corrupt and i
> should run "fsfsverify.py -f svn/repo/db/revs/7"?
You did back up the rev like the huge warning told you, right?
> After doing this, fsfsverify tells me: "Fixed? :-) Re-run
> fsfsverify without the -f option" and once I do this, it gives
> me an "Error InvalidWindow: ..." all the time, after each repair
> run with a different number.
Your rev can be corrupt in more than one location. fsfsverify only
fixes the first one that it finds. The fact that the number is
changing is actually a good thing. It likely means you have several
repeated blocks.
> Does this mean, I simply have to run it again and again until the
> error is gone? Or is the tool at its wit's end? And the repository
> corrupted beyond repair?
I've seen both sides. I have had to run the tool as much as 9 times
on some revisions because there were that many repeated blocks.
> Is there anything else (other than restore from the backup) I can do to
> recover the repository?
Restore from backup probably won't work. If the revision was corrupt
on the way in, then your backup has the corrupted rev as well.
Depending on the situation I've been able to recover the data, or
repair the rev if you have access to the correct revisions of specific
files that are corrupted (e.g., someone still has them in their
working copy, or they've been deployed to a web server so you still
have them around).
-John
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2365623
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: corrupted fsfs repository, tools for repair?
Posted by Ashwin Patil <as...@robosoftin.com>.
Even I had the same problem on the MAC OS X, and SVN version old version.
Upgrade your SVN as well as apache to new versions; it will stop corrupting
the more repositories.
----- Original Message -----
From: "Dirk Taggesell" <di...@proximic.com>
To: <us...@subversion.tigris.org>
Sent: Thursday, June 25, 2009 9:08 PM
Subject: corrupted fsfs repository, tools for repair?
> Dear subversion users,
>
> today I ran in a problem with my repository. The server is
> Mac OS X 10.4, subversion and apache are from the macports,
> the repository is accessed via apache and mod_dav_svn v. 1.4.0
> The repository stores data as FSFS.
>
> There has been an undetected filesystem error on the volume
> with the repository, corrupting it.
>
> Now if I want to check out, I receive errors like this:
> "svn: REPORT of '/svn/repo/!svn/vcc/default': Could not read
> chunk delimiter: Secure connection truncated"
>
> I copied the repository over to my Mac and tried to repair it
> using the current macports subversion 1.6.3.
>
> First I inspected the repository and "svnadmin verify" tells me:
> --- snip ---
> * Verified revision 0.
> * Verified revision 1.
> * Verified revision 2.
> * Verified revision 3.
> * Verified revision 4.
> * Verified revision 5.
> * Verified revision 6.
> svnadmin: Invalid diff stream: insn 2403 cannot be decoded
> --- snap ---
>
>
> A svnadmin recover seems to find nothing:
> --- snip ---
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> The latest repos revision is 17985.
> --- snap ---
>
> But it appears that it actually repairs nothing. As far as
> I've read the recover command is mainly for repositories using
> Berkeley db.
>
> Anyway, I then downloaded Mr. Zakmeisters fsfsverify, but I'm
> not entirely sure how to use it properly.
>
> So svnadmin verify stops at revision 6 and complains about
> "insn 2403". Does that mean that revision 7 is corrupt and i
> should run "fsfsverify.py -f svn/repo/db/revs/7"?
>
> After doing this, fsfsverify tells me: "Fixed? :-) Re-run
> fsfsverify without the -f option" and once I do this, it gives
> me an "Error InvalidWindow: ..." all the time, after each repair
> run with a different number.
>
> Does this mean, I simply have to run it again and again until the
> error is gone? Or is the tool at its wit's end? And the repository
> corrupted beyond repair?
>
> Is there anything else (other than restore from the backup) I can do to
> recover the repository?
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2365616
>
> To unsubscribe from this discussion, e-mail:
> [users-unsubscribe@subversion.tigris.org].
>
-----------------------------------------------
Robosoft Technologies - Come home to Technology
Disclaimer: This email may contain confidential material. If you were not an intended recipient, please notify the sender and delete all copies. Emails to and from our network may be logged and monitored. This email and its attachments are scanned for virus by our scanners and are believed to be safe. However, no warranty is given that this email is free of malicious content or virus.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2365625
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: corrupted fsfs repository, tools for repair?
Posted by Chris Watson <cw...@ptc.com>.
Keep running it until either the final error is fixed, or the fix
message stops changing.
If the latter - then your repo will need a more complicated and
destructive fixing process.
Note: You'll probably find that revisions after 7 are also corrupt -
with 17985 revisions you may be here for some time.
Chris
-----Original Message-----
From: Dirk Taggesell [mailto:dirk.taggesell@proximic.com]
Sent: 25 June 2009 18:39
To: users@subversion.tigris.org
Subject: corrupted fsfs repository, tools for repair?
Dear subversion users,
today I ran in a problem with my repository. The server is
Mac OS X 10.4, subversion and apache are from the macports,
the repository is accessed via apache and mod_dav_svn v. 1.4.0
The repository stores data as FSFS.
There has been an undetected filesystem error on the volume
with the repository, corrupting it.
Now if I want to check out, I receive errors like this:
"svn: REPORT of '/svn/repo/!svn/vcc/default': Could not read
chunk delimiter: Secure connection truncated"
I copied the repository over to my Mac and tried to repair it
using the current macports subversion 1.6.3.
First I inspected the repository and "svnadmin verify" tells me:
--- snip ---
* Verified revision 0.
* Verified revision 1.
* Verified revision 2.
* Verified revision 3.
* Verified revision 4.
* Verified revision 5.
* Verified revision 6.
svnadmin: Invalid diff stream: insn 2403 cannot be decoded
--- snap ---
A svnadmin recover seems to find nothing:
--- snip ---
Repository lock acquired.
Please wait; recovering the repository may take some time...
Recovery completed.
The latest repos revision is 17985.
--- snap ---
But it appears that it actually repairs nothing. As far as
I've read the recover command is mainly for repositories using
Berkeley db.
Anyway, I then downloaded Mr. Zakmeisters fsfsverify, but I'm
not entirely sure how to use it properly.
So svnadmin verify stops at revision 6 and complains about
"insn 2403". Does that mean that revision 7 is corrupt and i
should run "fsfsverify.py -f svn/repo/db/revs/7"?
After doing this, fsfsverify tells me: "Fixed? :-) Re-run
fsfsverify without the -f option" and once I do this, it gives
me an "Error InvalidWindow: ..." all the time, after each repair
run with a different number.
Does this mean, I simply have to run it again and again until the
error is gone? Or is the tool at its wit's end? And the repository
corrupted beyond repair?
Is there anything else (other than restore from the backup) I can do to
recover the repository?
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageI
d=2365616
To unsubscribe from this discussion, e-mail:
[users-unsubscribe@subversion.tigris.org].
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2365619
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].