John Peacock wrote:
> I have a scheduled update running every night that updates my APC
> (Archive of Perl Changes) repository with any patches applied. I just
> recreated it last weekend (using 0.34.0) and the autoupdates have run
> fine for several days (using 0.35.0-to-be).
>
> Last night, however, I was also dumping an old copy of the APC (from
> 0.27.0 days) into a new repository (on a different drive) when the
> auto-update started. I see lines these lines in the log:
>
>> 2003-12-17 00:04:35.946815500 svn: Unable to open an ra_local session
>> to URL
>> 2003-12-17 00:04:35.946878500 svn: Unable to open repository
>> 'file:///var/svn-repository/perl5/branches/maint-5.6'
>> 2003-12-17 00:04:35.946909500 svn: Berkeley DB error while opening
>> 'changes' table for filesystem /var/svn-repository/perl5/db:
>> 2003-12-17 00:04:35.946912500 Cannot allocate memory
>
>
> and now the repository itself is totally dead:
>
>> $ svnadmin recover /var/svn-repository/perl5
>> Please wait; recovering the repository may take some time...
>> svn: DB_RUNRECOVERY: Fatal error, run database recovery
>
>
> Even running Berkeley's db_recover yields little more than several
> screens of this:
>
>> db_recover: PANIC: fatal region error detected; run recovery
>> db_recover: PANIC: fatal region error detected; run recovery
>> ...
>> db_recover: PANIC: fatal region error detected; run recovery
>> db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database
>> recovery
>
>
> So it is completely hosed.
That's with asynchronous deltification turned on, right? Someone please
tell me that we're closing the FS environment before forking for
deltification, and that the forked process daemonizes itself before
opening the environment again.
--
Brane Čibej <brane_at_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
Received on Wed Dec 17 13:11:24 2003