You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Pejvan BEIGUI <pe...@online.fr> on 2004/07/16 01:17:48 UTC
database corruption
Hi All,
I'm not an old time user of Subversion but I've been quite happy with it
for the last three months.
But since today, I've got a very weird issue : I'm unable to do anything
with it, from checkouts to committing, with the folliwing errors :
> _pejvan_ trunk >> svn commit -m "cleaned up code for release"
> svn: Commit failed (details follow):
> svn: Berkeley DB error while checkpointing after Berkeley DB transaction for filesystem /Users/pejvan/Safe/subversion-repository/db:
> Invalid argument
> Abort
> _pejvan_ subversion-repository >> svnadmin verify /Users/pejvan/Safe/subversion-repository
> svn: Berkeley DB error while checkpointing after Berkeley DB transaction for filesystem /Users/pejvan/Safe/subversion-repository/db:
> Invalid argument
> svn: Berkeley DB error while closing 'nodes' database for filesystem /Users/pejvan/Safe/subversion-repository/db:
> Invalid argument
Has my database all the sudden get corrupted? I really don't understand
anything about what could possibly gone wrong and I couldn't find
anything any answer after googling and digging the mailing list archives.
How can I fix that?
How can I get my database information back?
I'm just about to install subversion for a whole team of developers, and
this could be a terrible issue if it had happened to them. No I'm quite
afraid of using subversion :-!
Thanks for your help in recovering my data!
Pejvan
--
Pejvan BEIGUI pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.
Re: database corruption
Posted by John Szakmeister <jo...@szakmeister.net>.
On Sunday 18 July 2004 13:49, Pejvan BEIGUI wrote:
[snip]
> You're absolutely right about all this. I have indeed a back-up of the
> last two days, and I felt really safe with this. The only thing which
> went wrong is that I haven't used svn for a few weeks and don't know
> why the base got corrupt and hence I didn't notice it and back-uped the
> corrupt DB. I guess that I'll add a daily incremental dump to another
> backup procedure.
If you make sure to run 'svnadmin recover' and 'svnadmin verify' on the
backed up repositories, that will help identify a corrupt repository.
That way, at least 1 of the 2 backup will be okay, and you don't have to
rely on accessing it yourself to identify corruption.
> Anyway, I'll keep on using SVN since I find it being a lot easier to
> use than CVS and it's also really more versatile :-)
I hear that. :-)
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: database corruption
Posted by Pejvan BEIGUI <pe...@online.fr>.
John Szakmeister wrote:
> On Friday 16 July 2004 13:14, Pejvan BEIGUI wrote:
> [snip]
>
>>This BDB thinguy starts to frightening me. And I'm about to install svn
>>for a whole team of developers, which frightens me even more now...
>>
>>Anyway, it's the right time to make a DVD-RW back-up I believe :-)
>>
>>Thanks again for your help.
>
>
> You may want to consider strengthening your backup process here too.
> Personally, I'm a bit paranoid when it comes to our source code, so all
> of our repositories are hotcopied into a backup directory. I run
> 'svnadmin recover' on each repository, as well as 'svnadmin dump' on each
> repo in the backup directory. Both the hotcopy and the dump are tarred
> and backed up to tape. All of this is done nightly as part of a cron
> job. This way, a maximum of one day may go by before I'm informed of any
> corruption (although, I'm certain one of my fellow developers would
> complain well before then :-). It may be overkill, but I feel
> comfortable in that I never have to worry about a severe loss of data.
>
> A more paranoid person would probably use the 'svnadmin dump
> --incremental' in conjuction with a post-commit hook script to save off
> commits during the day. Commit mails can also be useful in grabbing
> those few remaining revisions to restore as well (which we employ as both
> a method to restore missing revisions, and for code review). Note that
> commit mails generally don't contain binary data, so if you have a lot of
> that, 'svnadmin dump --incremental' is really the way to go.
>
> I can't stress how important it is to have a good backup solution. I
> sleep well at night knowing that our data is as safe as we can possibly
> make it, and that all isn't lost if/when a catastrophic failure or
> corruption occurs.
>
> That being said, if you have a good backup solution in place, there is
> nothing to fear. We've been using Subversion successfully since 0.17 and
> haven't lost one revision of data. All of our developers love the tool,
> and I love the fact that we can identify corruption before it gets to be
> a real problem, unlike CVS.
>
> -John
You're absolutely right about all this. I have indeed a back-up of the
last two days, and I felt really safe with this. The only thing which
went wrong is that I haven't used svn for a few weeks and don't know why
the base got corrupt and hence I didn't notice it and back-uped the
corrupt DB. I guess that I'll add a daily incremental dump to another
backup procedure.
Anyway, I'll keep on using SVN since I find it being a lot easier to use
than CVS and it's also really more versatile :-)
Pejvan
--
Pejvan BEIGUI pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.
Re: database corruption
Posted by John Szakmeister <jo...@szakmeister.net>.
On Friday 16 July 2004 13:14, Pejvan BEIGUI wrote:
[snip]
> This BDB thinguy starts to frightening me. And I'm about to install svn
> for a whole team of developers, which frightens me even more now...
>
> Anyway, it's the right time to make a DVD-RW back-up I believe :-)
>
> Thanks again for your help.
You may want to consider strengthening your backup process here too.
Personally, I'm a bit paranoid when it comes to our source code, so all
of our repositories are hotcopied into a backup directory. I run
'svnadmin recover' on each repository, as well as 'svnadmin dump' on each
repo in the backup directory. Both the hotcopy and the dump are tarred
and backed up to tape. All of this is done nightly as part of a cron
job. This way, a maximum of one day may go by before I'm informed of any
corruption (although, I'm certain one of my fellow developers would
complain well before then :-). It may be overkill, but I feel
comfortable in that I never have to worry about a severe loss of data.
A more paranoid person would probably use the 'svnadmin dump
--incremental' in conjuction with a post-commit hook script to save off
commits during the day. Commit mails can also be useful in grabbing
those few remaining revisions to restore as well (which we employ as both
a method to restore missing revisions, and for code review). Note that
commit mails generally don't contain binary data, so if you have a lot of
that, 'svnadmin dump --incremental' is really the way to go.
I can't stress how important it is to have a good backup solution. I
sleep well at night knowing that our data is as safe as we can possibly
make it, and that all isn't lost if/when a catastrophic failure or
corruption occurs.
That being said, if you have a good backup solution in place, there is
nothing to fear. We've been using Subversion successfully since 0.17 and
haven't lost one revision of data. All of our developers love the tool,
and I love the fact that we can identify corruption before it gets to be
a real problem, unlike CVS.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: database corruption on Mac OS X
Posted by Eric Ocean <bi...@masterpiece-ag.com>.
For what it's worth, I get the same errors when my Subversion
repository dies, and I'm confident that I have the versions matched
correctly, etc. I'm also on Mac OS X 10.3.4, so that might be what's
throwing people off with the BDB error messages.
Anyway, for guaranteed recoverability, just got to the db directory of
your repository and comment out the line in DB_CONFIG that says
setflags DB_LOG_AUTOREMOVE
This will keep your log files permanently, which you can backup to disc
if you don't want them to take up space. However, you'll need
(potentially) all of them when BDB needs to recover on Mac OS X. Even
though my repository is corrupted rather regularly, having the full set
of log files has allowed me to recover it every time. Don't trust the
output from db_recover -c. It'll say it failed (and give the same error
message!), but a subsequent verify indicates that it really succeeded,
and that everything is okay (which it is).
I think Subversion is plenty safe for your data. I've also looked at
the source (which I encourage everyone to do). It's clear that the
developers set the quality bar really high.
Regards,
Eric Ocean
On Jul 16, 2004, at 10:14 AM, Pejvan BEIGUI wrote:
> Max Bowsher wrote:
>
>>
>> Speculating:
>>
>> I suppose it might be possible for Berkeley DB's files to become
>> corrupted
>> in such a way that did not affect the data itself, but caused any
>> attempt to
>> allocate more space within those databases to fail.
>>
>> As to what might cause such subtle corruption - I have no idea.
>>
>> Max.
>>
> This BDB thinguy starts to frightening me. And I'm about to install svn
> for a whole team of developers, which frightens me even more now...
>
> Anyway, it's the right time to make a DVD-RW back-up I believe :-)
>
> Thanks again for your help.
>
> --
> Pejvan BEIGUI pejvan@online.fr
>
> Cet email comporte une signature electronique au format OpenPGP/MIME.
> Pour votre propre sécurité, tout email semblant provenir de cette
> adresse mais ne comportant pas de signature ou une signature
> non-valide sera réputé falsifié.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: database corruption
Posted by Pejvan BEIGUI <pe...@online.fr>.
Max Bowsher wrote:
>
> Speculating:
>
> I suppose it might be possible for Berkeley DB's files to become corrupted
> in such a way that did not affect the data itself, but caused any attempt to
> allocate more space within those databases to fail.
>
> As to what might cause such subtle corruption - I have no idea.
>
> Max.
>
This BDB thinguy starts to frightening me. And I'm about to install svn
for a whole team of developers, which frightens me even more now...
Anyway, it's the right time to make a DVD-RW back-up I believe :-)
Thanks again for your help.
--
Pejvan BEIGUI pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.
Re: database corruption
Posted by Max Bowsher <ma...@ukf.net>.
Pejvan BEIGUI wrote:
> Max Bowsher wrote:
>
>>> What's to do next ?
>>
>>
>> That's very odd.
>>
>> Try the same thing, but "svnadmin dump" instead of "svnadmin verify".
>>
>> If you can get a complete dump, then just load it into a new repository,
and
>> problem solved.
>>
>> If not, post error messages.
>>
>
> Max!
> You're the Man, you saved my day :-)
>
> dumping and reloading back seems to have solved the problem.
> I've made a few checkouts, commits, updates, and everything seems to be
> working again.
>
> Any idea about what could have possibly gone wrong ?
Speculating:
I suppose it might be possible for Berkeley DB's files to become corrupted
in such a way that did not affect the data itself, but caused any attempt to
allocate more space within those databases to fail.
As to what might cause such subtle corruption - I have no idea.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: database corruption
Posted by Pejvan BEIGUI <pe...@online.fr>.
Max Bowsher wrote:
>>What's to do next ?
>
>
> That's very odd.
>
> Try the same thing, but "svnadmin dump" instead of "svnadmin verify".
>
> If you can get a complete dump, then just load it into a new repository, and
> problem solved.
>
> If not, post error messages.
>
Max!
You're the Man, you saved my day :-)
dumping and reloading back seems to have solved the problem.
I've made a few checkouts, commits, updates, and everything seems to be
working again.
Any idea about what could have possibly gone wrong ?
Cheers,
Pejvan
--
Pejvan BEIGUI pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.
Re: database corruption
Posted by Max Bowsher <ma...@ukf.net>.
Pejvan BEIGUI wrote:
> Max Bowsher wrote:
>
>> Try this:
>>
>> Make a *copy* of your repository. Using this copy:
>>
>> Delete the __db.00* files from the db subdirectory of the repository.
>>
>> Run "svnadmin verify" on the repository.
>>
>> If it works, great, if not, post the exact error message.
>>
> rather good news (although very bizarre too!):
>> svnadmin recover /Users/pejvan/Safe/subversion-repository
>> Please wait; recovering the repository may take some time...
>> svn: DB_RUNRECOVERY: Fatal error, run database recovery
> and then:
>> svnadmin verify /Users/pejvan/Safe/subversion-repository
>> * Verified revision 0.
> [...]
>> * Verified revision 34.
>
> then I'm able to checkout the anything (or anything I tried).
> But I'm unable to commit and trying to commit makes again this :
>> svn commit -m "cleaned up code for release"
>> Sending main.m
>> Sending vidal-menu.xcode/pejvan.pbxuser
>> Sending vidalMenuObject.m
>> Transmitting file data ..Abort
>
>> svn log
>> svn: Unable to open an ra_local session to URL
>> svn: Unable to open repository
>> 'file:///Users/pejvan/Safe/subversion-repository/vidal-menu/trunk'
>> svn: Berkeley DB error while opening environment for filesystem
>> /Users/pejvan/Safe/subversion-repository/db: DB_RUNRECOVERY: Fatal error,
>> run database recovery
>
>> svn status
>> L .
>> M main.m
>> L French.lproj
>> L French.lproj/MainMenu.nib
>> L vidal-menu.xcode
>> M vidal-menu.xcode/pejvan.pbxuser
>> M vidalMenuObject.m
>> L English.lproj
>> L English.lproj/MainMenu.nib
>
>> svn log -r HEAD
>> svn: Unable to open an ra_local session to URL
>> svn: Unable to open repository
>> 'file:///Users/pejvan/Safe/subversion-repository/vidal-menu/trunk'
>> svn: Berkeley DB error while opening environment for filesystem
>> /Users/pejvan/Safe/subversion-repository/db: DB_RUNRECOVERY: Fatal error,
>> run database recovery
>
> Seems something is broken here.
>
> thanks a lot Max, Ben, Garrett for your help. You are very helpful and
> kind to help me get out of this mess :-)
>
> What's to do next ?
That's very odd.
Try the same thing, but "svnadmin dump" instead of "svnadmin verify".
If you can get a complete dump, then just load it into a new repository, and
problem solved.
If not, post error messages.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: database corruption
Posted by Pejvan BEIGUI <pe...@online.fr>.
Max Bowsher wrote:
> Try this:
>
> Make a *copy* of your repository. Using this copy:
>
> Delete the __db.00* files from the db subdirectory of the repository.
>
> Run "svnadmin verify" on the repository.
>
> If it works, great, if not, post the exact error message.
>
rather good news (although very bizarre too!):
> svnadmin recover /Users/pejvan/Safe/subversion-repository
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
and then:
> svnadmin verify /Users/pejvan/Safe/subversion-repository
> * Verified revision 0.
[...]
> * Verified revision 34.
then I'm able to checkout the anything (or anything I tried).
But I'm unable to commit and trying to commit makes again this :
> svn commit -m "cleaned up code for release"
> Sending main.m
> Sending vidal-menu.xcode/pejvan.pbxuser
> Sending vidalMenuObject.m
> Transmitting file data ..Abort
> svn log
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///Users/pejvan/Safe/subversion-repository/vidal-menu/trunk'
> svn: Berkeley DB error while opening environment for filesystem /Users/pejvan/Safe/subversion-repository/db:
> DB_RUNRECOVERY: Fatal error, run database recovery
> svn status
> L .
> M main.m
> L French.lproj
> L French.lproj/MainMenu.nib
> L vidal-menu.xcode
> M vidal-menu.xcode/pejvan.pbxuser
> M vidalMenuObject.m
> L English.lproj
> L English.lproj/MainMenu.nib
> svn log -r HEAD
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///Users/pejvan/Safe/subversion-repository/vidal-menu/trunk'
> svn: Berkeley DB error while opening environment for filesystem /Users/pejvan/Safe/subversion-repository/db:
> DB_RUNRECOVERY: Fatal error, run database recovery
Seems something is broken here.
thanks a lot Max, Ben, Garrett for your help. You are very helpful and
kind to help me get out of this mess :-)
What's to do next ?
Pejvan
--
Pejvan BEIGUI pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.
Re: database corruption
Posted by Max Bowsher <ma...@ukf.net>.
Pejvan BEIGUI wrote:
> OK, I'm having a headache now, since Fink automatically updated 1.0.4 to
> 1.0.5 and hence removed the old version. I have to find out a way to
> install the old version.
OK, then never mind with the otool stuff.
> I'm CCing Christian Schaffner who's the package maintainer of svn for
> Fink and who has been really helpful eachtime someone had a problem with
> svn. Maybe he can help?
Sounds like a good idea, get an OS X expert's opinion.
>> Or, maybe you could put a tarball of your repository files on a web/ftp
site
>> somewhere, and I'll investigate them.
>>
> This could be a solution, but I have my commercial projects in the
> repository,
> and I'm not sure my clients would appreciate this :(
Fair enough.
Try this:
Make a *copy* of your repository. Using this copy:
Delete the __db.00* files from the db subdirectory of the repository.
Run "svnadmin verify" on the repository.
If it works, great, if not, post the exact error message.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: database corruption
Posted by Christian Schaffner <ch...@users.sourceforge.net>.
On 16.07.2004, at 18:01, Pejvan BEIGUI wrote:
> OK, I'm having a headache now, since Fink automatically updated 1.0.4
> to
> 1.0.5 and hence removed the old version. I have to find out a way to
> install the old version.
Mhmm... there is no easy way to do that in fink. You could download the
old
1.0.4 version from
<http://cvs.sf.net/viewcvs.py/fink/dists/10.3/unstable/crypto/finkinfo/
svn-ssl.info>
and put it into your /sw/fink/dists/local/main/finkinfo/ directory.
Then run
% fink index
% fink install svn-ssl-1.0.4-12
to install the old version.
_However_: The fink svn packages build against db4.2 for a very long
time.
It does it since Feb 2nd 2004 with revision 0.37.0-11. So, unless you
had
a fink svn package from before, i don't see why you have a repository
built
with a svnadmin with db4.1.
So, i am not sure here.
Chris.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: database corruption
Posted by Pejvan BEIGUI <pe...@online.fr>.
Max Bowsher wrote:
> Pejvan BEIGUI wrote:
>
>>Garrett Rooney wrote:
>>
>>
>>>Pejvan BEIGUI wrote:
>>>
>>>
>>>>I'm using Mac OS X 10.3.4. I've built the svn sources using Fink
>>>>(fink.sf.net) and I have no idea of what "ldd" is, but it's not
>
> available
>
>>>>system. It seems that I'm using berkely db 4.2.52.
>>>
>>>
>>>The Mac OS X equivalent command is 'otool -L'.
>>>
>>
>>Oh great, thanks Garrett.
>>here's the output then :
>>
>>>>otool -L /sw/bin/svnadmin
>>>
>>>/sw/bin/svnadmin:
>>> /sw/lib/libdb-4.2.dylib (compatibility version 4.2.0, current
>>> version 4.2.52)
>
>
> OK, good, but we need the output from both your *old* and *new* svnadmin
> binary.
>
OK, I'm having a headache now, since Fink automatically updated 1.0.4 to
1.0.5 and hence removed the old version. I have to find out a way to
install the old version.
I'm CCing Christian Schaffner who's the package maintainer of svn for
Fink and who has been really helpful eachtime someone had a problem with
svn. Maybe he can help?
>
> Or, maybe you could put a tarball of your repository files on a web/ftp site
> somewhere, and I'll investigate them.
>
This could be a solution, but I have my commercial projects in the
repository,
and I'm not sure my clients would appreciate this :(
--
Pejvan BEIGUI pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.
Re: database corruption
Posted by Max Bowsher <ma...@ukf.net>.
Pejvan BEIGUI wrote:
> Garrett Rooney wrote:
>
>> Pejvan BEIGUI wrote:
>>
>>> I'm using Mac OS X 10.3.4. I've built the svn sources using Fink
>>> (fink.sf.net) and I have no idea of what "ldd" is, but it's not
available
>>> system. It seems that I'm using berkely db 4.2.52.
>>
>>
>> The Mac OS X equivalent command is 'otool -L'.
>>
> Oh great, thanks Garrett.
> here's the output then :
>>> otool -L /sw/bin/svnadmin
>> /sw/bin/svnadmin:
>> /sw/lib/libdb-4.2.dylib (compatibility version 4.2.0, current
>> version 4.2.52)
OK, good, but we need the output from both your *old* and *new* svnadmin
binary.
Or, maybe you could put a tarball of your repository files on a web/ftp site
somewhere, and I'll investigate them.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: database corruption
Posted by Pejvan BEIGUI <pe...@online.fr>.
Garrett Rooney wrote:
> Pejvan BEIGUI wrote:
>
>> I'm using Mac OS X 10.3.4. I've built the svn sources using Fink
>> (fink.sf.net) and I have no idea of what "ldd" is, but it's not available
>> system. It seems that I'm using berkely db 4.2.52.
>
>
> The Mac OS X equivalent command is 'otool -L'.
>
Oh great, thanks Garrett.
here's the output then :
>> otool -L /sw/bin/svnadmin
> /sw/bin/svnadmin:
> /sw/lib/libsvn_repos-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
> /sw/lib/libsvn_fs-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
> /sw/lib/libsvn_delta-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
> /sw/lib/libsvn_subr-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
> /sw/lib/libaprutil-0.0.dylib (compatibility version 10.0.0, current version 10.5.0)
> /sw/lib/libldap.2.dylib (compatibility version 3.0.0, current version 3.122.0)
> /sw/lib/libsasl2.2.dylib (compatibility version 3.0.0, current version 3.15.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.1.1)
> /sw/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7)
> /sw/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7)
> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos (compatibility version 5.0.0, current version 5.0.0)
> /sw/lib/libdb-4.2.dylib (compatibility version 4.2.0, current version 4.2.52)
> /sw/lib/liblber.2.dylib (compatibility version 3.0.0, current version 3.122.0)
> /sw/lib/libgdbm.3.dylib (compatibility version 4.0.0, current version 4.0.0)
> /sw/lib/libexpat.0.dylib (compatibility version 6.0.0, current version 6.0.0)
> /sw/lib/libiconv.2.dylib (compatibility version 5.0.0, current version 5.0.0)
> /sw/lib/libapr-0.0.dylib (compatibility version 10.0.0, current version 10.5.0)
> /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current version 324.5.0)
--
Pejvan BEIGUI pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.
Re: database corruption
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Pejvan BEIGUI wrote:
> I'm using Mac OS X 10.3.4. I've built the svn sources using Fink
> (fink.sf.net) and I have no idea of what "ldd" is, but it's not available
> system. It seems that I'm using berkely db 4.2.52.
The Mac OS X equivalent command is 'otool -L'.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: database corruption
Posted by Pejvan BEIGUI <pe...@online.fr>.
Ben Collins-Sussman wrote:
> On Fri, 2004-07-16 at 08:55, Pejvan BEIGUI wrote:
>
>
>>I've upgraded from version 1.0.4 to 1.0.5 but I didn't see any db
>>incompatibilities in the readme. Am I blind? :-)
>
>
> What does "upgraded" mean? Built from source? Installed a binary
> package? Whatever the case, it's likely that you have two different
> versions of BDB on your system, and 1.0.5 is a different one that 1.0.4
> is using. Try 'ldd svnadmin' to see what it's using.
>
I'm using Mac OS X 10.3.4. I've built the svn sources using Fink
(fink.sf.net) and I have no idea of what "ldd" is, but it's not available
system. It seems that I'm using berkely db 4.2.52.
Thanks for your great support and help and my apologies for my ignorance :-!
Pejvan
--
Pejvan BEIGUI pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.
Re: database corruption
Posted by Ben Collins-Sussman <su...@collab.net>.
On Fri, 2004-07-16 at 08:55, Pejvan BEIGUI wrote:
> I've upgraded from version 1.0.4 to 1.0.5 but I didn't see any db
> incompatibilities in the readme. Am I blind? :-)
What does "upgraded" mean? Built from source? Installed a binary
package? Whatever the case, it's likely that you have two different
versions of BDB on your system, and 1.0.5 is a different one that 1.0.4
is using. Try 'ldd svnadmin' to see what it's using.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: database corruption
Posted by Pejvan BEIGUI <pe...@online.fr>.
Ben Collins-Sussman wrote:
> Pejvan BEIGUI wrote:
>
>> How can I fix that?
>> How can I get my database information back?
>
>
> Surely, since you administer a database, you're making regular backups,
> right? And surely you've read all about the proper care and feeding of
> your database in chapter 5 of the book, right? :-)
>
I made daily backups, but the thing is, I keep only the backups of the
two last days on a second drive, so my 2 back-ups are screwed up. And
yes this may be a mistake but I also make backups every once in a while,
on a DVD-RW, but since I've been away for a few weeks, my DVD backup is
too old :(
Well, I've done nothing more than committing my changes, so I guess I
couldn't harm my DB this way, otherwise it really means that I should
quit using svn, right? :-)
> Have you tried 'svnadmin recover', running as the proper user?
>
This is what I get :
> $svnadmin recover /Users/pejvan/Safe/subversion-repository
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
> The 'invalid argument' thing looks like you've got mismatched BDB
> libraries. Like, one version of BDB trying to open a database created
> by a different version. Did you recently upgrade subversion or BDB?
>
>
I've upgraded from version 1.0.4 to 1.0.5 but I didn't see any db
incompatibilities in the readme. Am I blind? :-)
Thanks for your help,
Pejvan
--
Pejvan BEIGUI pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.
Re: database corruption
Posted by Ben Collins-Sussman <su...@collab.net>.
Pejvan BEIGUI wrote:
> How can I fix that?
> How can I get my database information back?
Surely, since you administer a database, you're making regular backups,
right? And surely you've read all about the proper care and feeding of
your database in chapter 5 of the book, right? :-)
Have you tried 'svnadmin recover', running as the proper user?
The 'invalid argument' thing looks like you've got mismatched BDB
libraries. Like, one version of BDB trying to open a database created
by a different version. Did you recently upgrade subversion or BDB?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org