You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Philip Martin <ph...@codematters.co.uk> on 2002/12/15 20:15:02 UTC
Re: can't create valid repositry
[Shivaken, dev@subversion.tigris.org is the list to use, not issues@s.t.o]
shivaken <sh...@jcom.home.ne.jp> writes:
> I am using subversion for 3 month.
> But, today I couldn't create valid repositry.
>
> $ svnadmin create testRepositry
> $ mkdir test
> $ touch test/testfile
> $ svn import file:///tmp/testRepositry test test -m"test"
> svn: Filesystem is corrupt
> svn: revision 0 missing from `revisions' table, in filesystem
> `/tmp/testRepositry/db'
>
> Then,
>
> $ svnadmin recover testRepositry
> Acquiring exclusive lock on repository db, and running recovery procedures.
> Please stand by...
> Recovery completed.
> svn: Filesystem is corrupt
> svn: revision 0 missing from `revisions' table, in filesystem
> `testRepositry/db'
>
> I'm using.
> linux-2.5.51 (SourceMage Gnu/Linux)
> glibc-2.3.1
> gcc-3.2.1
> db-4.0.14
Which version of Subversion?
Are you using svnadmin and svn from the same Subversion version?
Does this work
$ svnadmin create foo
$ svnlook youngest foo
$ svn co file://`pwd`/foo wc
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: can't create valid repositry
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
shivaken <sh...@jcom.home.ne.jp> writes:
> After all, in my SourceMage Linux system svnadmin can't create a valid
> repository.
We're not going to be able to do much with this, remotely -- we'll
need you to debug the bad repository. The debugging results may hint
as to what's going wrong with 'svnadmin create'.
Thanks,
-K
> On Wednesday 18 December 2002 00:55, Karl Fogel wrote:
> > Do you know how to run GDB? If you can run 'svnlook youngest foo' in
> > GDB, with a breakpoint on make_error_internal (you might have to break
> > in main() first, then set the other breakpoint), and see what's going
> > on when this error is made, that would probably tell us a lot.
> >
> > A glance at your repository doesn't show anything wrong, though I
> > could be missing something in the db_dump -da output.
> >
> > Yes, Berkeley 4.0.14 is the right one.
> >
> > Hmmm...
> >
> > -Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: can't create valid repositry
Posted by shivaken <sh...@jcom.home.ne.jp>.
Hi, Karl.
I installed subversion-r3578 to another machine(Mandrake Linux 8.0).
In that machine, All subversion's tools worked.
I wanted to clarify which is the problem's cause svn (and svnlook) or
repository created by svnadmin.
So, I copied a new repository from Mandrake to my machine has a trouble with
subversion.
Then, "svnlook youngest repository" and "svn import ..." worked.
After all, in my SourceMage Linux system svnadmin can't create a valid
repository.
On Wednesday 18 December 2002 00:55, Karl Fogel wrote:
> Do you know how to run GDB? If you can run 'svnlook youngest foo' in
> GDB, with a breakpoint on make_error_internal (you might have to break
> in main() first, then set the other breakpoint), and see what's going
> on when this error is made, that would probably tell us a lot.
>
> A glance at your repository doesn't show anything wrong, though I
> could be missing something in the db_dump -da output.
>
> Yes, Berkeley 4.0.14 is the right one.
>
> Hmmm...
>
> -Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: can't create valid repositry
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Do you know how to run GDB? If you can run 'svnlook youngest foo' in
GDB, with a breakpoint on make_error_internal (you might have to break
in main() first, then set the other breakpoint), and see what's going
on when this error is made, that would probably tell us a lot.
A glance at your repository doesn't show anything wrong, though I
could be missing something in the db_dump -da output.
Yes, Berkeley 4.0.14 is the right one.
Hmmm...
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: can't create valid repositry
Posted by shivaken <sh...@jcom.home.ne.jp>.
Hi, this is Result.
# ls -lR
/tmp/foo:
total 8
-rw-r--r-- 1 root root 376 Dec 16 19:35 README
drwxr-xr-x 2 root root 40 Dec 16 19:35 conf
drwxr-xr-x 2 root root 40 Dec 16 19:35 dav
drwxr-xr-x 2 root root 320 Dec 16 19:35 db
-rw-r--r-- 1 root root 2 Dec 16 19:35 format
drwxr-xr-x 2 root root 180 Dec 16 19:35 hooks
drwxr-xr-x 2 root root 60 Dec 16 19:35 locks
/tmp/foo/conf:
total 0
/tmp/foo/dav:
total 0
/tmp/foo/db:
total 744
-rw-r--r-- 1 root root 1182 Dec 16 19:35 DB_CONFIG
-rw-r--r-- 1 root root 8192 Dec 16 19:35 __db.001
-rw-r--r-- 1 root root 270336 Dec 16 19:35 __db.002
-rw-r--r-- 1 root root 327680 Dec 16 19:35 __db.003
-rw-r--r-- 1 root root 712704 Dec 16 19:35 __db.004
-rw-r--r-- 1 root root 16384 Dec 16 19:35 __db.005
-rw-r--r-- 1 root root 8192 Dec 16 19:35 changes
-rw-r--r-- 1 root root 8192 Dec 16 19:35 copies
-rw-r--r-- 1 root root 64922 Dec 16 19:36 log.0000000001
-rw-r--r-- 1 root root 8192 Dec 16 19:35 nodes
-rw-r--r-- 1 root root 8192 Dec 16 19:35 representations
-rw-r--r-- 1 root root 8192 Dec 16 19:35 revisions
-rw-r--r-- 1 root root 8192 Dec 16 19:35 strings
-rw-r--r-- 1 root root 8192 Dec 16 19:35 transactions
/tmp/foo/hooks:
total 28
-rw-r--r-- 1 root root 1286 Dec 16 19:35 post-commit.tmpl
-rw-r--r-- 1 root root 1474 Dec 16 19:35
post-revprop-change.tmpl
-rw-r--r-- 1 root root 1639 Dec 16 19:35 pre-commit.tmpl
-rw-r--r-- 1 root root 1952 Dec 16 19:35
pre-revprop-change.tmpl
-rw-r--r-- 1 root root 98 Dec 16 19:35 read-sentinels.tmpl
-rw-r--r-- 1 root root 1377 Dec 16 19:35 start-commit.tmpl
-rw-r--r-- 1 root root 100 Dec 16 19:35 write-sentinels.tmpl
/tmp/foo/locks:
total 4
-rw-r--r-- 1 root root 460 Dec 16 19:35 db.lock
# db_dump -da /tmp/foo/db/revisions
In-memory DB structure:
recno: 0x20060 (default page size, read-only, DB->open called)
bt_meta: 0 bt_root: 1
bt_maxkey: 0 bt_minkey: 2
bt_compare: 0x400383d7 bt_prefix: 0x4003846c
bt_lpgno: 0
re_pad: 0x20 re_delim: 0xa re_len: 0 re_source:
re_modified: 0 re_eof: 1 re_last: 0
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
page 0: btree metadata level: 0 (lsn.file: 1 lsn.offset: 13145)
magic: 0x53162
version: 8
pagesize: 4096
type: 9
keys: 0 records: 0
free list: 0
last_pgno: 1
flags: 0x2 (recno)
uid: 51 96 0 0 f 0 0 0 75 ac fd 3d c9 d9 1 0 0 0 0 0
maxkey: 0 minkey: 2
re_len: 0 re_pad: 32
root: 1
page 1: recno leaf level: 1 records: 0 (lsn.file: 1 lsn.offset: 13193)
prev: 0 next: 0 entries: 0 offset: 4096
# db_dump -da /tmp/foo/db/nodes
In-memory DB structure:
btree: 0x20060 (default page size, read-only, DB->open called)
bt_meta: 0 bt_root: 1
bt_maxkey: 0 bt_minkey: 2
bt_compare: 0x400383d7 bt_prefix: 0x4003846c
bt_lpgno: 0
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
page 0: btree metadata level: 0 (lsn.file: 1 lsn.offset: 4398)
magic: 0x53162
version: 8
pagesize: 4096
type: 9
keys: 0 records: 0
free list: 0
last_pgno: 1
flags: 0
uid: 50 96 0 0 f 0 0 0 75 ac fd 3d 29 53 0 0 0 0 0 0
maxkey: 0 minkey: 2
root: 1
page 1: btree leaf level: 1 (lsn.file: 1 lsn.offset: 4446)
prev: 0 next: 0 entries: 0 offset: 4096
Berkeley DB is 4.0.14. Is 4.0.24 needed?
Regards.
-- shivaken
On Monday 16 December 2002 23:25, you wrote:
> shivaken <sh...@jcom.home.ne.jp> writes:
> > $ svnadmin create foo
> > $ svnlook youngest foo
> > svn: Filesystem is corrupt
> > svn: revision 0 missing from `revisions' table, in filesystem `foo/db'
> > # svn co file:///tmp/foo wc
> > svn: Filesystem is corrupt
> > svn: revision 0 missing from `revisions' table, in filesystem
> > `/tmp/foo/db'
>
> Thanks for the thorough bug report.
>
> Yeah, this behavior is certainly wrong. I can't reproduce it, by the
> way. Please do
>
> ls -lR /tmp/foo
>
> and
>
> db_dump -da /tmp/foo/db/revisions
> db_dump -da /tmp/foo/db/nodes
>
> ...where `db_dump' is the right version of Berkeley DB 4.0.24's dump.
> For example, on my system, that's
>
> /usr/local/BerkeleyDB.4.0/bin/db_dump -da /tmp/foo
>
> Thanks,
> -Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: can't create valid repositry
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
shivaken <sh...@jcom.home.ne.jp> writes:
> $ svnadmin create foo
> $ svnlook youngest foo
> svn: Filesystem is corrupt
> svn: revision 0 missing from `revisions' table, in filesystem `foo/db'
> # svn co file:///tmp/foo wc
> svn: Filesystem is corrupt
> svn: revision 0 missing from `revisions' table, in filesystem `/tmp/foo/db'
Thanks for the thorough bug report.
Yeah, this behavior is certainly wrong. I can't reproduce it, by the
way. Please do
ls -lR /tmp/foo
and
db_dump -da /tmp/foo/db/revisions
db_dump -da /tmp/foo/db/nodes
...where `db_dump' is the right version of Berkeley DB 4.0.24's dump.
For example, on my system, that's
/usr/local/BerkeleyDB.4.0/bin/db_dump -da /tmp/foo
Thanks,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: can't create valid repositry
Posted by Philip Martin <ph...@codematters.co.uk>.
shivaken <sh...@jcom.home.ne.jp> writes:
> > >>Does this work
> > >>
> > >>$ svnadmin create foo
> > >>$ svnlook youngest foo
> > >>$ svn co file://`pwd`/foo wc
>
> Then, I did
>
> $ ./configure --prefix=/usr/local/subversion-r3987
> $ make
> # make install
> $ export PATH=/usr/local/subversion-r3987/bin:$PATH
> $ which svnadmin
> /usr/local/subversion-r3987/bin/svnadmin
> $ which svnlook
> /usr/local/subversion-r3987/bin/svnlook
> $ which svn
> /usr/local/subversion-r3987/bin/svn
> $ cd /tmp
> $ svnadmin create foo
> $ svnlook youngest foo
> svn: Filesystem is corrupt
> svn: revision 0 missing from `revisions' table, in filesystem `foo/db'
I don't know what could cause that.
Guessing at random, what do you get from
$ ldd /usr/local/subversion-r3987/bin/svnadmin
$ ldd /usr/local/subversion-r3987/bin/svnlook
are the correct shared libraries being used?
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: can't create valid repositry
Posted by shivaken <sh...@jcom.home.ne.jp>.
On Monday 16 December 2002 12:40, Branko Čibej wrote:
> >>Which version of Subversion?
> >>
> >>Are you using svnadmin and svn from the same Subversion version?
> >>
> >>Does this work
> >>
> >>$ svnadmin create foo
> >>$ svnlook youngest foo
> >>$ svn co file://`pwd`/foo wc
Then, I did
$ ./configure --prefix=/usr/local/subversion-r3987
$ make
# make install
$ export PATH=/usr/local/subversion-r3987/bin:$PATH
$ which svnadmin
/usr/local/subversion-r3987/bin/svnadmin
$ which svnlook
/usr/local/subversion-r3987/bin/svnlook
$ which svn
/usr/local/subversion-r3987/bin/svn
$ cd /tmp
$ svnadmin create foo
$ svnlook youngest foo
svn: Filesystem is corrupt
svn: revision 0 missing from `revisions' table, in filesystem `foo/db'
# svn co file:///tmp/foo wc
svn: Filesystem is corrupt
svn: revision 0 missing from `revisions' table, in filesystem `/tmp/foo/db'
I did this test with r3200, r3578, too.
(But svnlook dosen't have the option "youngest")
The Results are the same.
$ /usr/local/subversion-r3200/bin/svnadmin create foo2
$ /usr/local/subversion-r3200/bin/svn co file:///tmp/foo2 wc
svn: Filesystem is corrupt
svn: revision 0 missing from `revisions' table, in filesystem `/tmp/foo2/db'
$ /usr/local/subversion-r3578/bin/svnadmin create foo3
$ /usr/local/subversion-r3578/bin/svn co file:///tmp/foo3 wc
svn: Filesystem is corrupt
svn: revision 0 missing from `revisions' table, in filesystem `/tmp/foo3/db'
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: can't create valid repositry
Posted by Branko Čibej <br...@xbc.nu>.
shivaken wrote:
>Hi
>
>Sorry, I forgot. I tried r3200, r3578, r3987.
>
There was at least one database schema change during that time, I think.
>And, I installed them with --prefix=/usr.
>
>So, svnadmin and svn must be the same version.
>
I fail to see how you came to this conclusion.
>>Which version of Subversion?
>>
>>Are you using svnadmin and svn from the same Subversion version?
>>
>>Does this work
>>
>>$ svnadmin create foo
>>$ svnlook youngest foo
>>$ svn co file://`pwd`/foo wc
>>
Well, have you tried this recipe? The problem you report looks very much
like a schema mismatch, implying that your svnadmin and your svn are
from different versions.
BTW, why don't we have svnadmin --version?
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: can't create valid repositry
Posted by shivaken <sh...@jcom.home.ne.jp>.
Hi
Sorry, I forgot. I tried r3200, r3578, r3987.
And, I installed them with --prefix=/usr.
So, svnadmin and svn must be the same version.
> Which version of Subversion?
>
> Are you using svnadmin and svn from the same Subversion version?
>
> Does this work
>
> $ svnadmin create foo
> $ svnlook youngest foo
> $ svn co file://`pwd`/foo wc
Regards.
-- shivaken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org