You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Dale Peakall <da...@peakall.com> on 2003/11/04 09:59:09 UTC
Recovering corrupt repository
Disaster struck this morning, a classic blue-screen of death on my XP
box right in the middle of a commit. I've not been able to persuade
subversion to recover the repos.
Initially tried 'svnadmin recover' which seemed to work OK, but trying
to checkout a new copy of the repos resulted in:
svn: Filesystem is corrupt
svn: corrupt entry in `transactions' table for `1o' in filesystem
`c:/svn/db'
So I tried to use 'svnadmin rmtxns 1o' and got:
svn: Filesystem is corrupt
svn: svn_fs__rep_contents: checksum mismatch on rep "m7":
expected: 59c1e125a629d99be3a2881cd105e4bd
actual: bcd8b0c2eb1fce714eab6cef0d771acc
Next I gave 'svnadmin dump' a go and got the file-system is corrupt
error again after dumping a fair number of revisions. I think that this
has got all but commit that was in progress at the time of the crash in
it, but can't be completely sure as I don't pay much attention to the
revision number returned.
Will this dump be valid, or will the corrupt filesystem thang have made
a mess of the dump file that needs to be resolved by specifying the
revisions to dump?
Ta.
- Dale.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: make fails SuSE 9.0 correction
Posted by Robert <ro...@gmx.de>.
Am 04.11.2003 um 15:38 schrieb Patrick Mayweg:
> Hi Robert,
> Python.h lives in /usr/include/python2.3/ which I do not see in the
> list of
> your include directories.
> Regards,
> Patrick
>
That did the trick!
Thank you.
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: make fails SuSE 9.0 correction
Posted by Patrick Mayweg <ma...@qint.de>.
Hi Robert,
Python.h lives in /usr/include/python2.3/ which I do not see in the list of
your include directories.
Regards,
Patrick
Robert wrote:
> Hello.
> My make fails under SuSE 9.0 on 586 for svn 0.32.1. I am building a
> client only.
>
> Can somebody help, please?
>
> Phyton devel libs are installed as well as swig (the binary).
>
> Thank you!
>
> Robert
>
> cd subversion/tests/libsvn_delta && /bin/sh
> /home/welz/Sources/subversion-0.32.1/libtool --silent --mode=link gcc
> -g -O2 -g -O2 -pthread -DNEON_ZLIB -rpath /usr/local/lib -o
> vdelta-test vdelta-test.o
> ../../../subversion/libsvn_delta/libsvn_delta-1.la
> ../../../subversion/libsvn_subr/libsvn_subr-1.la
> /home/welz/Sources/subversion-0.32.1/apr-util/libaprutil-0.la -ldb1
> -lexpat /home/welz/Sources/subversion-0.32.1/apr/libapr-0.la -lrt -lm
> -lcrypt -lnsl -ldl
> /bin/sh /home/welz/Sources/subversion-0.32.1/libtool --silent
> --mode=compile gcc -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500
> -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DSWIGPYTHON -g -O2 -g -O2
> -pthread -DNEON_ZLIB -I./subversion/include -I.
> -I/home/welz/Sources/subversion-0.32.1/neon/src
> -I/usr/local/include/neon
> -I/home/welz/Sources/subversion-0.32.1/apr/include
> -I/home/welz/Sources/subversion-0.32.1/apr-util/include -o
> subversion/bindings/swig/swigutil_py.lo -c
> ./subversion/bindings/swig/swigutil_py.c
> subversion/bindings/swig/swigutil_py.c:20:20: Python.h: No such file or
> directory
> In file included from subversion/bindings/swig/swigutil_py.c:35:
> subversion/bindings/swig/swigutil_py.h:23:20: Python.h: No such file or
> directory
> In file included from subversion/bindings/swig/swigutil_py.c:35:
> subversion/bindings/swig/swigutil_py.h:54: error: parse error before
> '*' token
> subversion/bindings/swig/swigutil_py.h:54: warning: data definition has
> no type or storage class
> subversion/bindings/swig/swigutil_py.h:66: error: parse error before
> '*' token
> subversion/bindings/swig/swigutil_py.h:66: warning: data definition has
> no type or storage class
> subversion/bindings/swig/swigutil_py.h:69: error: parse error before
> '*' token
> subversion/bindings/swig/swigutil_py.h:69: warning: data definition has
> no type or storage class
> subversion/bindings/swig/swigutil_py.h:73: error: parse error before
> '*' token
> subversion/bindings/swig/swigutil_py.h:73: warning: data definition has
> no type or storage class
> subversion/bindings/swig/swigutil_py.h:77: error: parse error before
> '*' token
> subversion/bindings/swig/swigutil_py.h:77: warning: data definition has
> no type or storage class
> subversion/bindings/swig/swigutil_py.h:81: error: parse error before
> '*' token
> subversion/bindings/swig/swigutil_py.h:81: warning: data definition has
> no type or storage class
> subversion/bindings/swig/swigutil_py.h:88: error: parse error before
> '*' token
> subversion/bindings/swig/swigutil_py.h:94: error: parse error before
> "PyObject"
> subversion/bindings/swig/swigutil_py.h:97: error: parse error before
> '*' token
>
> ... snip
>
> make: *** [subversion/bindings/swig/swigutil_py.lo] Fehler 1
> welz@linux:~/Sources/subversion-0.32.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
make fails SuSE 9.0 correction
Posted by Robert <ro...@gmx.de>.
Hello.
My make fails under SuSE 9.0 on 586 for svn 0.32.1. I am building a
client only.
Can somebody help, please?
Phyton devel libs are installed as well as swig (the binary).
Thank you!
Robert
cd subversion/tests/libsvn_delta && /bin/sh
/home/welz/Sources/subversion-0.32.1/libtool --silent --mode=link gcc
-g -O2 -g -O2 -pthread -DNEON_ZLIB -rpath /usr/local/lib -o
vdelta-test vdelta-test.o
../../../subversion/libsvn_delta/libsvn_delta-1.la
../../../subversion/libsvn_subr/libsvn_subr-1.la
/home/welz/Sources/subversion-0.32.1/apr-util/libaprutil-0.la -ldb1
-lexpat /home/welz/Sources/subversion-0.32.1/apr/libapr-0.la -lrt -lm
-lcrypt -lnsl -ldl
/bin/sh /home/welz/Sources/subversion-0.32.1/libtool --silent
--mode=compile gcc -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500
-D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DSWIGPYTHON -g -O2 -g -O2
-pthread -DNEON_ZLIB -I./subversion/include -I.
-I/home/welz/Sources/subversion-0.32.1/neon/src
-I/usr/local/include/neon
-I/home/welz/Sources/subversion-0.32.1/apr/include
-I/home/welz/Sources/subversion-0.32.1/apr-util/include -o
subversion/bindings/swig/swigutil_py.lo -c
./subversion/bindings/swig/swigutil_py.c
subversion/bindings/swig/swigutil_py.c:20:20: Python.h: No such file or
directory
In file included from subversion/bindings/swig/swigutil_py.c:35:
subversion/bindings/swig/swigutil_py.h:23:20: Python.h: No such file or
directory
In file included from subversion/bindings/swig/swigutil_py.c:35:
subversion/bindings/swig/swigutil_py.h:54: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:54: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:66: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:66: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:69: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:69: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:73: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:73: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:77: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:77: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:81: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:81: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:88: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:94: error: parse error before
"PyObject"
subversion/bindings/swig/swigutil_py.h:97: error: parse error before
'*' token
... snip
make: *** [subversion/bindings/swig/swigutil_py.lo] Fehler 1
welz@linux:~/Sources/subversion-0.32.1>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
make fails SuSE 9.0
Posted by Robert <ro...@gmx.de>.
Hello.
My make fails under SuSE 9.0 on 586 for svn 0.32.1.
Can somebody help, please?
Phyton devel libs are installed as well as swig (the binary).
Thank you!
Robert
cd subversion/tests/libsvn_delta && /bin/sh
/home/welz/Sources/subversion-0.32.1/libtool --silent --mode=link gcc
-g -O2 -g -O2 -pthread -DNEON_ZLIB -rpath /usr/local/lib -o
vdelta-test vdelta-test.o
../../../subversion/libsvn_delta/libsvn_delta-1.la
../../../subversion/libsvn_subr/libsvn_subr-1.la
/home/welz/Sources/subversion-0.32.1/apr-util/libaprutil-0.la -ldb1
-lexpat /home/welz/Sources/subversion-0.32.1/apr/libapr-0.la -lrt -lm
-lcrypt -lnsl -ldl
/bin/sh /home/welz/Sources/subversion-0.32.1/libtool --silent
--mode=compile gcc -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500
-D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DSWIGPYTHON -g -O2 -g -O2
-pthread -DNEON_ZLIB -I./subversion/include -I.
-I/home/welz/Sources/subversion-0.32.1/neon/src
-I/usr/local/include/neon
-I/home/welz/Sources/subversion-0.32.1/apr/include
-I/home/welz/Sources/subversion-0.32.1/apr-util/include -o
subversion/bindings/swig/swigutil_py.lo -c
./subversion/bindings/swig/swigutil_py.c
subversion/bindings/swig/swigutil_py.c:20:20: Python.h: No such file or
directory
In file included from subversion/bindings/swig/swigutil_py.c:35:
subversion/bindings/swig/swigutil_py.h:23:20: Python.h: No such file or
directory
In file included from subversion/bindings/swig/swigutil_py.c:35:
subversion/bindings/swig/swigutil_py.h:54: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:54: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:66: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:66: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:69: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:69: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:73: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:73: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:77: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:77: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:81: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:81: warning: data definition has
no type or storage class
subversion/bindings/swig/swigutil_py.h:88: error: parse error before
'*' token
subversion/bindings/swig/swigutil_py.h:94: error: parse error before
"PyObject"
subversion/bindings/swig/swigutil_py.h:97: error: parse error before
'*' token
... snip
make: *** [subversion/bindings/swig/swigutil_py.lo] Fehler 1
welz@linux:~/Sources/subversion-0.32.1>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Recovering corrupt repository
Posted by kf...@collab.net.
"Dale Peakall" <da...@peakall.com> writes:
> Next I gave 'svnadmin dump' a go and got the file-system is corrupt
> error again after dumping a fair number of revisions. I think that this
> has got all but commit that was in progress at the time of the crash in
> it, but can't be completely sure as I don't pay much attention to the
> revision number returned.
Can you look at the revision dates (see the svn:date property on
revisions in the dumpfile) to determine if you got them all?
> Will this dump be valid, or will the corrupt filesystem thang have made
> a mess of the dump file that needs to be resolved by specifying the
> revisions to dump?
If you know the last complete revision N in the dumpfile, just run
'svnadmin dump -r0:N', that should produce a clean dumpfile.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org