[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Property editing issue across versions

From: Dirk-Willem van Gulik <dirkx_at_webweaving.org>
Date: 2003-06-30 20:31:12 CEST

On Mon, 30 Jun 2003, Greg Stein wrote:

> Looking at the error log, it would seem the client submitted the wrong
> namespace for the log message. That would indicate an old client. Yet Dirk
> says the client is at 0.24.2. Weird!

-> double check of versions; all at 0.24.2 on FreeBSD 5.0. However there
is one difference; on the clients which broke the commit-ability
apr-config gives:

        $ apr-config
        /usr/ports/devel/apr/work/apr-0.9.3 not found.

whereas on the other machine source is still present and the output is
simply '0.9.4'.

-> file:/// did allow me to do a commit (whereas http:/// did not).

Ok - a bit of 'sed' making sure there are no properties which did not
start with svn: in the proplist's seemed to have done the trick. I am now
allowed to commit again. The error has disappeared.

However I did needed to do a

        db_recover: Finding last valid log LSN: file: 226 offset 148393
        db_recover: Checkpoint at: [226][148345]
        db_recover: Checkpoint LSN: [226][148345]
        db_recover: Previous checkpoint: [226][147647]
        db_recover: Checkpoint at: [226][147647]
        db_recover: Checkpoint LSN: [226][147647]
        db_recover: Previous checkpoint: [226][146949]
        db_recover: Recovery complete at Mon Jun 30 11:19:44 2003
        db_recover: Maximum transaction id 80000000 Recovery checkpoint [226][148345]

shortly after this;

        [Mon Jun 30 11:10:19 2003] [error] [client] (20014)Error
        string not specified yet: Berkeley DB error while closing `nodes' database
        for filesystem /data3/subversion/repos/db:

which was after the first svn commit after the propset cleanup with a sed
script. But now all seems fine and stable again.

A svnadmin dump and a diff confirms that the wacking of the illegal
properties is the only change. Nothing else was changed. So the error
propably can be ignored.

Would love to know what the source of this issue is. It kind of feels like
loosing a file system and beeing at the mercy of an fsck you do not quite
understand. Digging futher and trying to understand :-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 30 20:32:17 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.