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
Received on Fri Jul 16 17:59:26 2004