You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jonas Voss <jo...@gmail.com> on 2004/09/06 20:12:08 UTC
svn: No transaction named '4v' in filesystem '/usr/local/repos/db'
Hi there,
I am getting this error whenever I try to list, commit or checkout
proejcts with svn.
I am running svn 1.1.0rc2 on Mac OS X 10.3.5, and had a short
poweroutage earlier today. After the outage the machine rebooted, and
I checked out a project which gave me some errormessages afterwards.
The exact wording escapes me unfortunately, but I believe it had
something to do with some bytes not being readable.
By the way, does svn log it's output to anywhere pr. default on OS X?
I can't find anything on my system about its doings.
Anywho, I tried to check out another project and I get this:
[20:54] voss@zaphod ~ > svn co file:///usr/local/repos/bb
svn: No transaction named '4v' in filesystem '/usr/local/repos/db'
So, realising a backup was too late, I tar'ed /usr/local/repos, and
tried to run db4_verify on the __db.* files in the original repos. I
get this:
zaphod:/usr/local/repos/db root # db4_verify __db.001
db_verify: Page 0: bad magic number 419430400
db_verify: Page 0: bad page size 0
db_verify: DB->verify: __db.001: DB_VERIFY_BAD: Database verification failed
zaphod:/usr/local/repos/db root # db4_verify __db.002
db_verify: Page 0: pgno incorrectly set to 1
db_verify: Page 0: bad magic number 16777216
db_verify: Page 0: bad page size 1
db_verify: Page 1: partially zeroed page
db_verify: DB->verify: __db.002: DB_VERIFY_BAD: Database verification failed
zaphod:/usr/local/repos/db root # db4_verify __db.003
db_verify: Page 0: pgno incorrectly set to 64608
db_verify: Page 0: bad magic number 4244635647
db_verify: Page 0: bad page size 0
db_verify: DB->verify: __db.003: DB_VERIFY_BAD: Database verification failed
zaphod:/usr/local/repos/db root # db4_verify __db.004
db_verify: Page 0: pgno incorrectly set to 4294967295
db_verify: Page 0: bad magic number 4244635647
db_verify: Page 0: bad page size 0
db_verify: Page 1: partially zeroed page
db_verify: Page 2: partially zeroed page
db_verify: Page 3: partially zeroed page
db_verify: Page 4: partially zeroed page
db_verify: DB->verify: __db.004: DB_VERIFY_BAD: Database verification failed
zaphod:/usr/local/repos/db root # db4_verify __db.005
db_verify: Page 0: pgno incorrectly set to 4294967295
db_verify: Page 0: bad magic number 4244635647
db_verify: Page 0: bad page size 0
db_verify: DB->verify: __db.005: DB_VERIFY_BAD: Database verification failed
Last resort, I try svnadmin verify on the repository and get this:
[20:55] voss@zaphod local/repos/db > svnadmin verify $REPOS_PATH
* 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.
* Verified revision 9.
* Verified revision 10.
* Verified revision 11.
* Verified revision 12.
* Verified revision 13.
* Verified revision 14.
* Verified revision 15.
* Verified revision 16.
* Verified revision 17.
* Verified revision 18.
* Verified revision 19.
* Verified revision 20.
* Verified revision 21.
* Verified revision 22.
* Verified revision 23.
* Verified revision 24.
* Verified revision 25.
* Verified revision 26.
* Verified revision 27.
* Verified revision 28.
* Verified revision 29.
* Verified revision 30.
* Verified revision 31.
* Verified revision 32.
* Verified revision 33.
* Verified revision 34.
* Verified revision 35.
* Verified revision 36.
* Verified revision 37.
* Verified revision 38.
* Verified revision 39.
* Verified revision 40.
* Verified revision 41.
* Verified revision 42.
* Verified revision 43.
* Verified revision 44.
* Verified revision 45.
* Verified revision 46.
* Verified revision 47.
* Verified revision 48.
* Verified revision 49.
* Verified revision 50.
* Verified revision 51.
* Verified revision 52.
* Verified revision 53.
* Verified revision 54.
* Verified revision 55.
* Verified revision 56.
* Verified revision 57.
* Verified revision 58.
* Verified revision 59.
* Verified revision 60.
svn: No such string '1jt'
[21:02] voss@zaphod local/repos/db >
I then run svnadmin recover on the repository:
[20:51] voss@zaphod local/repos/db > svnadmin recover $REPOS_PATH
Please wait; recovering the repository may take some time...
svn: DB_RUNRECOVERY: Fatal error, run database recovery
svn: bdb: Log sequence error: page LSN 120 954456; previous LSN 121 688063
svn: bdb: Recovery function for LSN 121 738783 failed on forward pass
svn: bdb: PANIC: Invalid argument
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
svn: bdb: PANIC: fatal region error detected; run recovery
[20:52] voss@zaphod local/repos/db >
I do some more verification a couple of times, and still get the above
message. Then I ran svnadmin recover again and get this:
[21:02] voss@zaphod local/repos/db > svnadmin recover $REPOS_PATH
Please wait; recovering the repository may take some time...
Recovery completed.
The latest repos revision is 93.
[21:03] voss@zaphod local/repos/db >
Which tells me, that everything is honky-dory.
I then try to get a list of the repository and get:
[21:03] voss@zaphod ~ > svn list file://$REPOS_PATH
svn: No transaction named '4v' in filesystem '/usr/local/repos/db'
I then tried using db4_recover like so on the db folder of the repos:
zaphod:/usr/local/repos/db root # db4_recover -c -e -v
db_recover: Finding last valid log LSN: file: 121 offset 901358
db_recover: DB_LOGC->get: LSN 120/1006494: invalid log record header
db_recover: Recovery starting from [120][28]
Segmentation fault
zaphod:/usr/local/repos/db root #
I then tried svnadmin recover again:
[21:39] voss@zaphod ~ > svnadmin recover /usr/local/repos
Please wait; recovering the repository may take some time...
And it has been doing this for 30 minutes. Is this normal? I can see
my repository is about 100Mb big, so maybe 30+ minutes is to be
expected for a recovery.
Does anyone have any views on this? Anything is greatly appreciated.
Cheers, Jonas.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: No transaction named '4v' in filesystem '/usr/local/repos/db'
Posted by Jonas Voss <jo...@gmail.com>.
Hi Max,
On Tue, 7 Sep 2004 08:33:03 +0100, Max Bowsher <ma...@ukf.net> wrote:
> Your repository looks quite nastily damaged.
> Put the tarball on a web/ftp site, email me the URL, and I'll assess the
> damage, and attempt recovery if possible.
What an excellent service! You could really save my day on this one.
I am currently uploading the tarball for you, and emailed a URL for
you to retrieve it.
I've also put a tarball of svnadmin dump $REPOS_PATH in there, even
though the dump is only about 5Mb.
Once again, thanks for trying to fix this for me, and I promise to
make regular backups from now on (:
Cheers, Jonas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: No transaction named '4v' in filesystem '/usr/local/repos/db'
Posted by Max Bowsher <ma...@ukf.net>.
Jonas Voss wrote:
> Hi there,
>
> I am getting this error whenever I try to list, commit or checkout
> proejcts with svn.
>
> I am running svn 1.1.0rc2 on Mac OS X 10.3.5, and had a short
> poweroutage earlier today. After the outage the machine rebooted, and
> I checked out a project which gave me some errormessages afterwards.
> The exact wording escapes me unfortunately, but I believe it had
> something to do with some bytes not being readable.
>
> By the way, does svn log it's output to anywhere pr. default on OS X?
> I can't find anything on my system about its doings.
>
> Anywho, I tried to check out another project and I get this:
>
> [20:54] voss@zaphod ~ > svn co file:///usr/local/repos/bb
> svn: No transaction named '4v' in filesystem '/usr/local/repos/db'
....
Your repository looks quite nastily damaged.
Put the tarball on a web/ftp site, email me the URL, and I'll assess the
damage, and attempt recovery if possible.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org