You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Garry Hill <ga...@ascii-turf.net> on 2004/07/15 15:39:01 UTC
what do i do now?
hi, i don't know what went wrong or when but by reading various postings to/from this list i've migrated from a
svnadmin recover ./SVN
Please wait; recovering the repository may take some time...
svn: DB_RUNRECOVERY: Fatal error, run database recovery
to a:
% db4_recover -h ./SVN/db
db_recover: Ignoring log file: ./SVN/db/log.0000000001: magic number 0, not 40988
db_recover: Invalid log file: log.0000000001: Invalid argument
db_recover: First log record not found
db_recover: PANIC: Invalid argument
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
to a:
-rw-r--r-- 1 garry staff 831666 15 Jul 11:34 log.0000000004
-rw-r--r-- 1 garry staff 1047385 5 Jul 12:39 log.0000000003
-rw-r--r-- 1 garry staff 479385 12 Jul 10:49 log.0000000001
cp -R SVN/db .
rm SVN/log.0000000001
to a:
% svnadmin recover SVN
Please wait; recovering the repository may take some time...
Recovery completed.
The latest repos revision is 31.
(with a <phew>)
to a:
% svn ci -m "re-wrote interface code"
svn: Commit failed (details follow):
svn: No transaction named '15' in filesystem '/Volumes/biscuit/Creation/dev/konfabulator/SVN/db'
and a:
% svnadmin lstxns
<nothing>
and a:
% svnadmin verify SVN
* Verified revision 0.
* Verified revision 1.
* Verified revision 2.
* Verified revision 3.
* Verified revision 4.
* Verified revision 5.
* Verified revision 6.
* Verified revision 7.
* Verified revision 8.
svn: No transaction named 'b' in filesystem 'SVN/db'
... now i'm stuck. i can dump but only up to revision 8. the thing is i'm not really worried about the previous revisions, there's a lot of chaff in there and my current working version is the best i've ever had. but, what's the best way to proceed from here? and, how can i stop this happening again/what went wrong?
i'm the only user of the repos, it's not open through apache or anything like that. i saw no sign of svn crashes or weirdness when checking in my revisions. my machine did go a bit wonky a couple of times but not while i was actively using the repos or even soon after. it is possible that disk corruption happened but it seems unlikely.
many thanks,
Garry
----------- version info
Mac OS 10.3.4
Darwin hostname.local 7.4.0 Darwin Kernel Version 7.4.0
svn, version 1.0.4 (r9844)
compiled Jul 15 2004, 12:01:21
% otool -L `which svn`
/opt/local/bin/svn:
/opt/local/lib/libsvn_client-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_wc-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_diff-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_ra-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_ra_local-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_repos-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_fs-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_ra_dav-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_ra_svn-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_delta-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libsvn_subr-1.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libaprutil-0.0.dylib (compatibility version 10.0.0, current version 10.4.0)
/opt/local/lib/libdb-4.2.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libiconv.2.dylib (compatibility version 5.0.0, current version 5.0.0)
/opt/local/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)
/opt/local/lib/libneon.24.dylib (compatibility version 25.0.0, current version 25.6.0)
/usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7)
/usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/local/lib/libexpat.0.dylib (compatibility version 6.0.0, current version 6.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.1.1)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: what do i do now?
Posted by Eric Ocean <bi...@masterpiece-ag.com>.
I'm on Mac OS X, have the same errors, and installed both Subversion
and BDB directly from the source, so I don't think it's a problem with
Fink or DarwinPorts (I have neither installed).
I don't think it's an OS thing though; I think it's a BDB thing.
Regards,
Eric Ocean
On Jul 16, 2004, at 12:49 PM, Garry Hill wrote:
>> I think disk corruption is *extremely* likely to be the cause of this.
>>
>> If you like, post a tarball of your repository on a web/ftp site, and
>> I will
>> assess the damage, and repair it if possible.
>
> Thanks Max, you're a star, I've sent you a link off-list.
>
> Is it just me, or do there seem to be a lot of "my db is corrupted"
> wails coming from us mac os x users? there's a concurrent thread with
> mine from Pejvan BEIGUI who is using the same system as me but with
> svn installed via fink rather than darwin ports as i used. I dug a lot
> of info out of old threads that, as far as i remember, also tended to
> be mac os x users.
>
> is this an os thing? or is it more likely to be the rather peculiar
> conjunction of versions and patches used by the various package/port
> systems?
>
> anyway, i'm concerned. fsfs here i come...
>
> g
>
> Max Bowsher [Friday, July 16, 2004] wrote:
>
>> Garry Hill wrote:
>>> my machine did go a bit wonky a couple of times but not while i
>>> was actively using the repos or even soon after. it is possible that
>>> disk
>>> corruption happened but it seems unlikely.
>>
>> Based on this:
>> (the log.1 dated after log.3)
>>
>>> -rw-r--r-- 1 garry staff 831666 15 Jul 11:34 log.0000000004
>>> -rw-r--r-- 1 garry staff 1047385 5 Jul 12:39 log.0000000003
>>> -rw-r--r-- 1 garry staff 479385 12 Jul 10:49 log.0000000001
>>
>> and this:
>>
>>> svn: No transaction named 'b' in filesystem 'SVN/db'
>>
>> and this:
>> (note the version numbers!)
>>
>>> /opt/local/lib/libdb-4.2.dylib (compatibility version 0.0.0,
>> current
>>> version 0.0.0)
>>
>> I think disk corruption is *extremely* likely to be the cause of this.
>>
>> If you like, post a tarball of your repository on a web/ftp site, and
>> I will
>> assess the damage, and repair it if possible.
>>
>> Max.
>>
>>
>> -- Original Email in full--
>> Garry Hill wrote:
>>> hi, i don't know what went wrong or when but by reading various
>>> postings
>>> to/from this list i've migrated from a
>>>
>>> svnadmin recover ./SVN
>>> Please wait; recovering the repository may take some time...
>>> svn: DB_RUNRECOVERY: Fatal error, run database recovery
>>>
>>> to a:
>>>
>>> % db4_recover -h ./SVN/db
>>> db_recover: Ignoring log file: ./SVN/db/log.0000000001: magic number
>>> 0,
>> not
>>> 40988
>>> db_recover: Invalid log file: log.0000000001: Invalid argument
>>> db_recover: First log record not found
>>> db_recover: PANIC: Invalid argument
>>> db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database
>> recovery
>>>
>>> to a:
>>>
>>> -rw-r--r-- 1 garry staff 831666 15 Jul 11:34 log.0000000004
>>> -rw-r--r-- 1 garry staff 1047385 5 Jul 12:39 log.0000000003
>>> -rw-r--r-- 1 garry staff 479385 12 Jul 10:49 log.0000000001
>>>
>>> cp -R SVN/db .
>>> rm SVN/log.0000000001
>>>
>>> to a:
>>>
>>> % svnadmin recover SVN
>>> Please wait; recovering the repository may take some time...
>>>
>>> Recovery completed.
>>> The latest repos revision is 31.
>>>
>>> (with a <phew>)
>>>
>>> to a:
>>>
>>> % svn ci -m "re-wrote interface code"
>>> svn: Commit failed (details follow):
>>> svn: No transaction named '15' in filesystem
>>> '/Volumes/biscuit/Creation/dev/konfabulator/SVN/db'
>>>
>>> and a:
>>>
>>> % svnadmin lstxns
>>> <nothing>
>>>
>>> and a:
>>>
>>> % svnadmin verify SVN
>>> * Verified revision 0.
>>> * Verified revision 1.
>>> * Verified revision 2.
>>> * Verified revision 3.
>>> * Verified revision 4.
>>> * Verified revision 5.
>>> * Verified revision 6.
>>> * Verified revision 7.
>>> * Verified revision 8.
>>> svn: No transaction named 'b' in filesystem 'SVN/db'
>>>
>>> ... now i'm stuck. i can dump but only up to revision 8. the thing
>>> is i'm
>> not
>>> really worried about the previous revisions, there's a lot of chaff
>>> in
>> there
>>> and my current working version is the best i've ever had. but,
>>> what's the
>>> best way to proceed from here? and, how can i stop this happening
>> again/what
>>> went wrong?
>>>
>>> i'm the only user of the repos, it's not open through apache or
>>> anything
>> like
>>> that. i saw no sign of svn crashes or weirdness when checking in my
>>> revisions. my machine did go a bit wonky a couple of times but not
>>> while i
>>> was actively using the repos or even soon after. it is possible that
>>> disk
>>> corruption happened but it seems unlikely.
>>>
>>> many thanks,
>>>
>>> Garry
>>>
>>> ----------- version info
>>>
>>> Mac OS 10.3.4
>>> Darwin hostname.local 7.4.0 Darwin Kernel Version 7.4.0
>>> svn, version 1.0.4 (r9844)
>>> compiled Jul 15 2004, 12:01:21
>>>
>>> % otool -L `which svn`
>>> /opt/local/bin/svn:
>>> /opt/local/lib/libsvn_client-1.0.dylib (compatibility version
>> 1.0.0,
>>> current version 1.0.0)
>>> /opt/local/lib/libsvn_wc-1.0.dylib (compatibility version
>>> 1.0.0,
>>> current version 1.0.0)
>>> /opt/local/lib/libsvn_diff-1.0.dylib (compatibility version
>>> 1.0.0,
>>> current version 1.0.0)
>>> /opt/local/lib/libsvn_ra-1.0.dylib (compatibility version
>>> 1.0.0,
>>> current version 1.0.0)
>>> /opt/local/lib/libsvn_ra_local-1.0.dylib (compatibility
>>> version
>>> 1.0.0, current version 1.0.0)
>>> /opt/local/lib/libsvn_repos-1.0.dylib (compatibility version
>> 1.0.0,
>>> current version 1.0.0)
>>> /opt/local/lib/libsvn_fs-1.0.dylib (compatibility version
>>> 1.0.0,
>>> current version 1.0.0)
>>> /opt/local/lib/libsvn_ra_dav-1.0.dylib (compatibility version
>> 1.0.0,
>>> current version 1.0.0)
>>> /opt/local/lib/libsvn_ra_svn-1.0.dylib (compatibility version
>> 1.0.0,
>>> current version 1.0.0)
>>> /opt/local/lib/libsvn_delta-1.0.dylib (compatibility version
>> 1.0.0,
>>> current version 1.0.0)
>>> /opt/local/lib/libsvn_subr-1.0.dylib (compatibility version
>>> 1.0.0,
>>> current version 1.0.0)
>>> /opt/local/lib/libaprutil-0.0.dylib (compatibility version
>>> 10.0.0,
>>> current version 10.4.0)
>>> /opt/local/lib/libdb-4.2.dylib (compatibility version 0.0.0,
>> current
>>> version 0.0.0)
>>> /usr/lib/libiconv.2.dylib (compatibility version 5.0.0,
>>> current
>>> version 5.0.0)
>>> /opt/local/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)
>>> /opt/local/lib/libneon.24.dylib (compatibility version
>>> 25.0.0,
>>> current version 25.6.0)
>>> /usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7,
>>> current
>>> version 0.9.7)
>>> /usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.7,
>> current
>>> version 0.9.7)
>>> /usr/lib/libz.1.dylib (compatibility version 1.0.0, current
>> version
>>> 1.0.0)
>>> /opt/local/lib/libexpat.0.dylib (compatibility version 6.0.0,
>> current
>>> version 6.0.0)
>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
>>> current
>>> version 71.1.1)
>>
>
> ---------------------------------------------------------------------
> 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
Re: what do i do now?
Posted by Garry Hill <ga...@ascii-turf.net>.
> Regarding your specific repository:
> Somehow, log.3, log.4 and transactions had been severely corrupted with what
> appears to be random blocks of data from elsewhere on the disc. (other
> tables were also slightly affected)
>
> You were lucky, because only the transactions table was badly affected - if
> the transactions table is destroyed but the others are intact, the only loss
> of data are the revprops (i.e. log author and date).
> You were doubly lucky, in that although the transactions table was badly
> damaged, I was able to locate the uncorrupted data for each transaction skel
> (the format of data svn uses within bdb) by viewing the db file in a text
> editor, and doing copy/paste, thereby recovering all the data.
and a bloody marvel it is too. thanks max! re-loaded repos working like a charm, it doesn't even blush when i give it a hard look.
> Interesting side-note to any svn developers who know the bdb schema, who are
> reading this:
> Despite being mainly uncorrupted, all but one of the tables with a next-key
> row had that row reset to value "c".
hmmm... i was hoping that i might learn how to do this recovery thing but i think i'll just forget it.
> Anyway, so, repository fully recovered, and fsfs seems like quite a good
> idea for OS X users.
doesn't it just.
g
> Max.
>
>
> ---------------------------------------------------------------------
> 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
Re: what do i do now?
Posted by Max Bowsher <ma...@ukf.net>.
Garry Hill wrote:
>> I think disk corruption is *extremely* likely to be the cause of this.
>>
>> If you like, post a tarball of your repository on a web/ftp site, and I
will
>> assess the damage, and repair it if possible.
>
> Thanks Max, you're a star, I've sent you a link off-list.
>
> Is it just me, or do there seem to be a lot of "my db is corrupted" wails
> coming from us mac os x users? there's a concurrent thread with mine from
> Pejvan BEIGUI who is using the same system as me but with svn installed
via
> fink rather than darwin ports as i used. I dug a lot of info out of old
> threads that, as far as i remember, also tended to be mac os x users.
>
> is this an os thing? or is it more likely to be the rather peculiar
> conjunction of versions and patches used by the various package/port
systems?
>
> anyway, i'm concerned. fsfs here i come...
You are right, there do seem to a quite a few corrupt dbs coming from OS X
users.
I haven't been keeping count to give exact statistics, though.
BDB 4.1 was known to be a recipe for disaster on OS X. Perhaps whatever OS X
specific bug was present in 4.1 hasn't been completely fixed in 4.2?
Regarding your specific repository:
Somehow, log.3, log.4 and transactions had been severely corrupted with what
appears to be random blocks of data from elsewhere on the disc. (other
tables were also slightly affected)
You were lucky, because only the transactions table was badly affected - if
the transactions table is destroyed but the others are intact, the only loss
of data are the revprops (i.e. log author and date).
You were doubly lucky, in that although the transactions table was badly
damaged, I was able to locate the uncorrupted data for each transaction skel
(the format of data svn uses within bdb) by viewing the db file in a text
editor, and doing copy/paste, thereby recovering all the data.
Interesting side-note to any svn developers who know the bdb schema, who are
reading this:
Despite being mainly uncorrupted, all but one of the tables with a next-key
row had that row reset to value "c".
Anyway, so, repository fully recovered, and fsfs seems like quite a good
idea for OS X users.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: what do i do now?
Posted by Garry Hill <ga...@ascii-turf.net>.
> I think disk corruption is *extremely* likely to be the cause of this.
>
> If you like, post a tarball of your repository on a web/ftp site, and I will
> assess the damage, and repair it if possible.
Thanks Max, you're a star, I've sent you a link off-list.
Is it just me, or do there seem to be a lot of "my db is corrupted" wails coming from us mac os x users? there's a concurrent thread with mine from Pejvan BEIGUI who is using the same system as me but with svn installed via fink rather than darwin ports as i used. I dug a lot of info out of old threads that, as far as i remember, also tended to be mac os x users.
is this an os thing? or is it more likely to be the rather peculiar conjunction of versions and patches used by the various package/port systems?
anyway, i'm concerned. fsfs here i come...
g
Max Bowsher [Friday, July 16, 2004] wrote:
> Garry Hill wrote:
> > my machine did go a bit wonky a couple of times but not while i
> > was actively using the repos or even soon after. it is possible that disk
> > corruption happened but it seems unlikely.
>
> Based on this:
> (the log.1 dated after log.3)
>
> > -rw-r--r-- 1 garry staff 831666 15 Jul 11:34 log.0000000004
> > -rw-r--r-- 1 garry staff 1047385 5 Jul 12:39 log.0000000003
> > -rw-r--r-- 1 garry staff 479385 12 Jul 10:49 log.0000000001
>
> and this:
>
> > svn: No transaction named 'b' in filesystem 'SVN/db'
>
> and this:
> (note the version numbers!)
>
> > /opt/local/lib/libdb-4.2.dylib (compatibility version 0.0.0,
> current
> > version 0.0.0)
>
> I think disk corruption is *extremely* likely to be the cause of this.
>
> If you like, post a tarball of your repository on a web/ftp site, and I will
> assess the damage, and repair it if possible.
>
> Max.
>
>
> -- Original Email in full--
> Garry Hill wrote:
> > hi, i don't know what went wrong or when but by reading various postings
> > to/from this list i've migrated from a
> >
> > svnadmin recover ./SVN
> > Please wait; recovering the repository may take some time...
> > svn: DB_RUNRECOVERY: Fatal error, run database recovery
> >
> > to a:
> >
> > % db4_recover -h ./SVN/db
> > db_recover: Ignoring log file: ./SVN/db/log.0000000001: magic number 0,
> not
> > 40988
> > db_recover: Invalid log file: log.0000000001: Invalid argument
> > db_recover: First log record not found
> > db_recover: PANIC: Invalid argument
> > db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database
> recovery
> >
> > to a:
> >
> > -rw-r--r-- 1 garry staff 831666 15 Jul 11:34 log.0000000004
> > -rw-r--r-- 1 garry staff 1047385 5 Jul 12:39 log.0000000003
> > -rw-r--r-- 1 garry staff 479385 12 Jul 10:49 log.0000000001
> >
> > cp -R SVN/db .
> > rm SVN/log.0000000001
> >
> > to a:
> >
> > % svnadmin recover SVN
> > Please wait; recovering the repository may take some time...
> >
> > Recovery completed.
> > The latest repos revision is 31.
> >
> > (with a <phew>)
> >
> > to a:
> >
> > % svn ci -m "re-wrote interface code"
> > svn: Commit failed (details follow):
> > svn: No transaction named '15' in filesystem
> > '/Volumes/biscuit/Creation/dev/konfabulator/SVN/db'
> >
> > and a:
> >
> > % svnadmin lstxns
> > <nothing>
> >
> > and a:
> >
> > % svnadmin verify SVN
> > * Verified revision 0.
> > * Verified revision 1.
> > * Verified revision 2.
> > * Verified revision 3.
> > * Verified revision 4.
> > * Verified revision 5.
> > * Verified revision 6.
> > * Verified revision 7.
> > * Verified revision 8.
> > svn: No transaction named 'b' in filesystem 'SVN/db'
> >
> > ... now i'm stuck. i can dump but only up to revision 8. the thing is i'm
> not
> > really worried about the previous revisions, there's a lot of chaff in
> there
> > and my current working version is the best i've ever had. but, what's the
> > best way to proceed from here? and, how can i stop this happening
> again/what
> > went wrong?
> >
> > i'm the only user of the repos, it's not open through apache or anything
> like
> > that. i saw no sign of svn crashes or weirdness when checking in my
> > revisions. my machine did go a bit wonky a couple of times but not while i
> > was actively using the repos or even soon after. it is possible that disk
> > corruption happened but it seems unlikely.
> >
> > many thanks,
> >
> > Garry
> >
> > ----------- version info
> >
> > Mac OS 10.3.4
> > Darwin hostname.local 7.4.0 Darwin Kernel Version 7.4.0
> > svn, version 1.0.4 (r9844)
> > compiled Jul 15 2004, 12:01:21
> >
> > % otool -L `which svn`
> > /opt/local/bin/svn:
> > /opt/local/lib/libsvn_client-1.0.dylib (compatibility version
> 1.0.0,
> > current version 1.0.0)
> > /opt/local/lib/libsvn_wc-1.0.dylib (compatibility version 1.0.0,
> > current version 1.0.0)
> > /opt/local/lib/libsvn_diff-1.0.dylib (compatibility version 1.0.0,
> > current version 1.0.0)
> > /opt/local/lib/libsvn_ra-1.0.dylib (compatibility version 1.0.0,
> > current version 1.0.0)
> > /opt/local/lib/libsvn_ra_local-1.0.dylib (compatibility version
> > 1.0.0, current version 1.0.0)
> > /opt/local/lib/libsvn_repos-1.0.dylib (compatibility version
> 1.0.0,
> > current version 1.0.0)
> > /opt/local/lib/libsvn_fs-1.0.dylib (compatibility version 1.0.0,
> > current version 1.0.0)
> > /opt/local/lib/libsvn_ra_dav-1.0.dylib (compatibility version
> 1.0.0,
> > current version 1.0.0)
> > /opt/local/lib/libsvn_ra_svn-1.0.dylib (compatibility version
> 1.0.0,
> > current version 1.0.0)
> > /opt/local/lib/libsvn_delta-1.0.dylib (compatibility version
> 1.0.0,
> > current version 1.0.0)
> > /opt/local/lib/libsvn_subr-1.0.dylib (compatibility version 1.0.0,
> > current version 1.0.0)
> > /opt/local/lib/libaprutil-0.0.dylib (compatibility version 10.0.0,
> > current version 10.4.0)
> > /opt/local/lib/libdb-4.2.dylib (compatibility version 0.0.0,
> current
> > version 0.0.0)
> > /usr/lib/libiconv.2.dylib (compatibility version 5.0.0, current
> > version 5.0.0)
> > /opt/local/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)
> > /opt/local/lib/libneon.24.dylib (compatibility version 25.0.0,
> > current version 25.6.0)
> > /usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current
> > version 0.9.7)
> > /usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.7,
> current
> > version 0.9.7)
> > /usr/lib/libz.1.dylib (compatibility version 1.0.0, current
> version
> > 1.0.0)
> > /opt/local/lib/libexpat.0.dylib (compatibility version 6.0.0,
> current
> > version 6.0.0)
> > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
> > version 71.1.1)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: what do i do now?
Posted by Max Bowsher <ma...@ukf.net>.
Garry Hill wrote:
> my machine did go a bit wonky a couple of times but not while i
> was actively using the repos or even soon after. it is possible that disk
> corruption happened but it seems unlikely.
Based on this:
(the log.1 dated after log.3)
> -rw-r--r-- 1 garry staff 831666 15 Jul 11:34 log.0000000004
> -rw-r--r-- 1 garry staff 1047385 5 Jul 12:39 log.0000000003
> -rw-r--r-- 1 garry staff 479385 12 Jul 10:49 log.0000000001
and this:
> svn: No transaction named 'b' in filesystem 'SVN/db'
and this:
(note the version numbers!)
> /opt/local/lib/libdb-4.2.dylib (compatibility version 0.0.0,
current
> version 0.0.0)
I think disk corruption is *extremely* likely to be the cause of this.
If you like, post a tarball of your repository on a web/ftp site, and I will
assess the damage, and repair it if possible.
Max.
-- Original Email in full--
Garry Hill wrote:
> hi, i don't know what went wrong or when but by reading various postings
> to/from this list i've migrated from a
>
> svnadmin recover ./SVN
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
>
> to a:
>
> % db4_recover -h ./SVN/db
> db_recover: Ignoring log file: ./SVN/db/log.0000000001: magic number 0,
not
> 40988
> db_recover: Invalid log file: log.0000000001: Invalid argument
> db_recover: First log record not found
> db_recover: PANIC: Invalid argument
> db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database
recovery
>
> to a:
>
> -rw-r--r-- 1 garry staff 831666 15 Jul 11:34 log.0000000004
> -rw-r--r-- 1 garry staff 1047385 5 Jul 12:39 log.0000000003
> -rw-r--r-- 1 garry staff 479385 12 Jul 10:49 log.0000000001
>
> cp -R SVN/db .
> rm SVN/log.0000000001
>
> to a:
>
> % svnadmin recover SVN
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> The latest repos revision is 31.
>
> (with a <phew>)
>
> to a:
>
> % svn ci -m "re-wrote interface code"
> svn: Commit failed (details follow):
> svn: No transaction named '15' in filesystem
> '/Volumes/biscuit/Creation/dev/konfabulator/SVN/db'
>
> and a:
>
> % svnadmin lstxns
> <nothing>
>
> and a:
>
> % svnadmin verify SVN
> * Verified revision 0.
> * Verified revision 1.
> * Verified revision 2.
> * Verified revision 3.
> * Verified revision 4.
> * Verified revision 5.
> * Verified revision 6.
> * Verified revision 7.
> * Verified revision 8.
> svn: No transaction named 'b' in filesystem 'SVN/db'
>
> ... now i'm stuck. i can dump but only up to revision 8. the thing is i'm
not
> really worried about the previous revisions, there's a lot of chaff in
there
> and my current working version is the best i've ever had. but, what's the
> best way to proceed from here? and, how can i stop this happening
again/what
> went wrong?
>
> i'm the only user of the repos, it's not open through apache or anything
like
> that. i saw no sign of svn crashes or weirdness when checking in my
> revisions. my machine did go a bit wonky a couple of times but not while i
> was actively using the repos or even soon after. it is possible that disk
> corruption happened but it seems unlikely.
>
> many thanks,
>
> Garry
>
> ----------- version info
>
> Mac OS 10.3.4
> Darwin hostname.local 7.4.0 Darwin Kernel Version 7.4.0
> svn, version 1.0.4 (r9844)
> compiled Jul 15 2004, 12:01:21
>
> % otool -L `which svn`
> /opt/local/bin/svn:
> /opt/local/lib/libsvn_client-1.0.dylib (compatibility version
1.0.0,
> current version 1.0.0)
> /opt/local/lib/libsvn_wc-1.0.dylib (compatibility version 1.0.0,
> current version 1.0.0)
> /opt/local/lib/libsvn_diff-1.0.dylib (compatibility version 1.0.0,
> current version 1.0.0)
> /opt/local/lib/libsvn_ra-1.0.dylib (compatibility version 1.0.0,
> current version 1.0.0)
> /opt/local/lib/libsvn_ra_local-1.0.dylib (compatibility version
> 1.0.0, current version 1.0.0)
> /opt/local/lib/libsvn_repos-1.0.dylib (compatibility version
1.0.0,
> current version 1.0.0)
> /opt/local/lib/libsvn_fs-1.0.dylib (compatibility version 1.0.0,
> current version 1.0.0)
> /opt/local/lib/libsvn_ra_dav-1.0.dylib (compatibility version
1.0.0,
> current version 1.0.0)
> /opt/local/lib/libsvn_ra_svn-1.0.dylib (compatibility version
1.0.0,
> current version 1.0.0)
> /opt/local/lib/libsvn_delta-1.0.dylib (compatibility version
1.0.0,
> current version 1.0.0)
> /opt/local/lib/libsvn_subr-1.0.dylib (compatibility version 1.0.0,
> current version 1.0.0)
> /opt/local/lib/libaprutil-0.0.dylib (compatibility version 10.0.0,
> current version 10.4.0)
> /opt/local/lib/libdb-4.2.dylib (compatibility version 0.0.0,
current
> version 0.0.0)
> /usr/lib/libiconv.2.dylib (compatibility version 5.0.0, current
> version 5.0.0)
> /opt/local/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)
> /opt/local/lib/libneon.24.dylib (compatibility version 25.0.0,
> current version 25.6.0)
> /usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current
> version 0.9.7)
> /usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.7,
current
> version 0.9.7)
> /usr/lib/libz.1.dylib (compatibility version 1.0.0, current
version
> 1.0.0)
> /opt/local/lib/libexpat.0.dylib (compatibility version 6.0.0,
current
> version 6.0.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
> version 71.1.1)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org