You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Eric S. Raymond" <es...@snark.thyrsus.com> on 2006/02/19 05:14:03 UTC
Inexcusable BDB upgrade triple blunder
Once before I flamed the Subversion dev group over an unbelievable sequence of
blunders, slipshod programming, and culpable obliviousness to the situation
of actual users. Looks like it's time I have to do it again, and once again
the botch combines a broken administrative procedure with pathetically
inadequate documentation and an alleged recovery path that's a mirage.
Yes, this means I've tripped over the 4.2->4.3 BDB upgrade problem.
My symptoms:
svn: Unable to open an ra_local session to URL
svn: Unable to open repository 'file:///home/esr/WWW/shipper/SVN/trunk/README'
svn: Berkeley DB error for filesystem /home/esr/WWW/shipper/SVN/db while opening environment:
DB_VERSION_MISMATCH: Database environment version mismatch
svn: bdb: Program version 4.3 doesn't match environment version
First blunder: screwing up db_recover() so a current svnadmin can't be
used to upgrade the repository. But that would have been OK, except for...
Second blunder: the FAQ answer. Fix it with an older version of
svnadmin? Sounds like a peachy idea -- until the svnadmin run fails
because it doesn't see the right version of the SVN repo shared libraries to
dynamic-link to. A 100% predictable roadblock about which the
FAQ entry says *nothing*.
Oh, and by the way, there's that marvelously vague instruction to
'make a backup'. Why? With what? And how does one tell if one needs
to *use* the backup? In general, this FAQ entry is so dizzyingly
useless to anyone who doesn't inhabit the skull of a Subversion
developer that one is left to wonder that kind of drugs the dolt who
wrote it was on.
Here, too, the lossage could easily have been contained -- by carrying
links to downloadable statically linked svnadmin42 binaries for major
platforms in the FAQ entry. But no. That would have made too much sense.
Third blunder: Instead, diligent Googling turned up a set of recovery
instructions bypassing svnadmin and using the db* utilities. Except
that when applied on the most commonly deployed Linux distribution
(Fedora Core) the instructions don't actually, you know, *work* or
anything. I'm referring to this:
http://lists.alioth.debian.org/pipermail/pkg-subversion-maintainers/2005-November/000268.html
Buoyed up by the naive confidence that a reply I found on the
Subversion dev list itself might embody something resembling a clue, I
did as it suggested and wrote a script, intending to donate it back to
the project. Here it is:
------------------------------------------------------------------------------
#!/bin/sh
#
# Upgrade a local SVN repo from BDB 4.2. Follows the instructions in
# http://lists.alioth.debian.org/pipermail/pkg-subversion-maintainers/2005-November/000268.html
#
repo=$1
db42_checkpoint -1 -h ${repo}/db
db42_recover -h ${repo}/db
db42_archive -d -h ${repo}/db
rm ${repo}/db/__db.???
------------------------------------------------------------------------------
Notice that I couldn't actually follow the instructions, because the db utility
names weren't right. I fixed them, and ran the script, and got this:
db_checkpoint: open: No such file or directory
db_recover: Ignoring log file: SVN/db/log.0000000004: unsupported log version 10
db_recover: Invalid log file: log.0000000004: Invalid argument
db_recover: PANIC: Invalid argument
db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
db_archive: Ignoring log file: SVN/db/log.0000000004: unsupported log version 10
db_archive: Invalid log file: log.0000000004: Invalid argument
db_archive: PANIC: Invalid argument
db_archive: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_archive: open: DB_RUNRECOVERY: Fatal error, run database recovery
rm: cannot remove `SVN/db/__db.???': No such file or directory
And yes, I did check that the repo path was correct. (It pretty much
has to be for the second error line to have been generated.)
But I should not have had to try writing a recovery script iun the
first place. I can see by the date of the aforementioned posting that
this bug has been a known problem for *three* *months*. That tells me
there is zero excuse for there not to have been a fix script
downloadable through the Subversion FAQ page and dated at least two
and a half months ago.
What in the fleeping frack were you guys *thinking*? Or, more likely,
not-thinking. It's guaranteed that this same problem is going to mug
anyone who updates from the 1.1.4 stock on FC4 to 1.2.3. You've now
left anybody who relied on your upgrade path with invisibly broken
repositories and no way out for at least *eight* *weeks*.
That's inexcusable. Whoever is responsible for this triple-play of
incompetence should be deeply ashamed. It reflects badly in the entire
dev group.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
In the absence of any evidence tending to show that possession
or use of a 'shotgun having a barrel of less than eighteen inches
in length' at this time has some reasonable relationship to the
preservation or efficiency of a well regulated militia, we cannot
say that the Second Amendment guarantees the right to keep and bear
such an instrument. [...] The Militia comprised all males
physically capable of acting in concert for the common defense.
-- Majority Supreme Court opinion in "U.S. vs. Miller" (1939)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 2/27/06, Branko Čibej <br...@xbc.nu> wrote:
>
> Here's the problem:
>
> * We have a global cache of open BDB environment descriptors. This
> cache is of course allocated from a (global) pool, and each
> descriptor gets its own subpool. The cached descriptors are
> reference-counted.
> * Each svn_fs_t owns a handle to one of these descriptors. These
> handles (actually, their allocators and pool cleanups) manage the
> descriptor reference counts.
>
> So far so good. Everything works beautifully, no memory leaks anywhere.
> Sheer paradise ...
>
> ... except for one nasty problem. The global pool for the cache can be
> created *after* the first svn_fs_t is allocated (from a different pool).
> Because we have no requirement about library initialization order in
> 1.x, we can only create the cache when it's first needed, not, say, just
> after apr_initialize.
>
> The consequence is that, when we hit apr_terminate, the cache's pool can
> be destroyed before the pool that contains the svn_fs_t that refers to
> the cache; that's because APR destroys its (global) pools in LIFO order.
> Unfortunately that means that during destruction of the svn_fs_t, we try
> to access memory that's already been freed.
>
> I've pretty much convinced myself that this can only happen during
> apr_terminate, but that's not much help, because it can still
> potentially cause a crash (or worse).
>
> I can't change the pool cleanup order short of a) hacking the pool
> structure directly (eek!), or b) requiring that svn_fs_initialize be
> called right after apr_initialize (ook ... er, that is, impossible).
>
> I've considered using malloc to allocate the descriptors, but i'd still
> need a pool per descriptor for open file handles, utf8->native
> translation of database paths, etc.
>
>
> I'm sure that, with all the brainpower on this list, someone will come
> up with a trivially elegant solution to this problem.
>
> So ... any bright ideas?
How about double-indirection pointers?
When the svn_fs_t takes an element from the cache, have the svn_fs_t leave a
pointer back to that svn_fs_t's pointer within the cache item. This allows
the cache pool cleanup to NULL the pointer back in the original svn_fs_t.
When the svn_fs_t goes to cleanup, if it sees that the pointer is NULL, it
knows that it already cleaned up and not to access any of the memory
associated with the cached item. -- justin
Re: Inexcusable BDB upgrade triple blunder
Posted by Branko Čibej <br...@xbc.nu>.
Philip Martin wrote:
> Branko Čibej <br...@xbc.nu> writes:
>
>
>> Which reminds me that I forgot to mention a tiny detail: the relation
>> between svn_fs_t's and cached environments is many-to-one. IOW, I'd
>> have to put a dictionary of open handles into the descriptor.
>>
>
> Install a pool cleanup for each handle, thus using the pool's
> dictionary.
>
Hey, that _is_ brilliant!
(/me bangs head against wall, muttering something about not having
though of that)
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Philip Martin <ph...@codematters.co.uk>.
Branko Čibej <br...@xbc.nu> writes:
> Which reminds me that I forgot to mention a tiny detail: the relation
> between svn_fs_t's and cached environments is many-to-one. IOW, I'd
> have to put a dictionary of open handles into the descriptor.
Install a pool cleanup for each handle, thus using the pool's
dictionary.
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 2/28/06, Branko Čibej <br...@xbc.nu> wrote:
>
> I _have_ a simple refcount. I can't invalidate the handles on cache
> cleanup if I don't have a reference to them, yes?
That's where the double-indirection pointers come in. -- justin
Re: Inexcusable BDB upgrade triple blunder
Posted by Branko Čibej <br...@xbc.nu>.
Justin Erenkrantz wrote:
> On 2/28/06, *Branko Čibej* <brane@xbc.nu <ma...@xbc.nu>> wrote:
>
> Which reminds me that I forgot to mention a tiny detail: the relation
> between svn_fs_t's and cached environments is many-to-one. IOW,
> I'd have
> to put a dictionary of open handles into the descriptor. I'd also have
> to add a validity check on the svn_fs_t's environment usage in _every_
> BDB-related operation in the back-end. That's doable, but it's a mess,
> and error-prone.
>
>
> Why wouldn't a simple refcount work? (incremented when passed out,
> decremented on cleanup)
>
> I'm not seeing why you'd need a dictionary of open handles... -- justin
I _have_ a simple refcount. I can't invalidate the handles on cache
cleanup if I don't have a reference to them, yes?
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 2/28/06, Branko Čibej <br...@xbc.nu> wrote:
>
> Which reminds me that I forgot to mention a tiny detail: the relation
> between svn_fs_t's and cached environments is many-to-one. IOW, I'd have
> to put a dictionary of open handles into the descriptor. I'd also have
> to add a validity check on the svn_fs_t's environment usage in _every_
> BDB-related operation in the back-end. That's doable, but it's a mess,
> and error-prone.
Why wouldn't a simple refcount work? (incremented when passed out,
decremented on cleanup)
I'm not seeing why you'd need a dictionary of open handles... -- justin
Re: Inexcusable BDB upgrade triple blunder
Posted by Branko Čibej <br...@xbc.nu>.
Garrett Rooney wrote:
> On 2/27/06, Branko Čibej <br...@xbc.nu> wrote:
>
>
>> So ... any bright ideas?
>>
>
> How about the following hare-brained scheme:
>
> Have the BDB env handles and filesystem objects both store pointers to
> each other, so the first one that has a pool cleanup fire can NULL out
> the pointers that refer to it? That way the second one to fire can't
> get back to the free'd memory.
>
Ah, yes, you and Justin came up with the same idea.
Which reminds me that I forgot to mention a tiny detail: the relation
between svn_fs_t's and cached environments is many-to-one. IOW, I'd have
to put a dictionary of open handles into the descriptor. I'd also have
to add a validity check on the svn_fs_t's environment usage in _every_
BDB-related operation in the back-end. That's doable, but it's a mess,
and error-prone.
Another potential problem with this scheme is thread-safety; as long as
the descriptor only invalidates the svn_fs_t's handles during
apr_terminate, we can safely ignore that.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Branko Čibej <br...@xbc.nu>.
Jim Blandy wrote:
> You know, this may be an argument for a new APR operation:
>
> /* Ensure that the pool ENDURING will be freed after the pool
> TRANSIENT. The two pools must have some common ancestor pool
> (possibly the root pool --- is there a root pool?), and ENDURING must
> be an immediate child of that ancestor pool. */
> void apr_free_pool_after (apr_pool_t *enduring, apr_pool_t *transient);
>
> Then you'd always ensure the cache pool was going to be freed after
> whatever pool was containing the svn_fs_t.
>
Yes, I was thinking along those lines, too (all APR pools have a common
ancestor, there's exactly one "really" global pool in APR). The trouble
is that changes to APR tend to take quite a while to show up in
distributions. And, this being a new API, we'd only be able to add it in
APR's trunk, not back-port is to the released branches.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Jim Blandy <ji...@red-bean.com>.
On 2/27/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> On 2/27/06, Branko Čibej <br...@xbc.nu> wrote:
>
> > So ... any bright ideas?
>
> How about the following hare-brained scheme:
>
> Have the BDB env handles and filesystem objects both store pointers to
> each other, so the first one that has a pool cleanup fire can NULL out
> the pointers that refer to it? That way the second one to fire can't
> get back to the free'd memory.
I think this is the best you can do. If you don't have some way for
the cache to tell its users that it has gone away, then the cache's
lifetime must be a superset of all its users' lifetimes. And there's
no way to get a pool that does that.
You know, this may be an argument for a new APR operation:
/* Ensure that the pool ENDURING will be freed after the pool
TRANSIENT. The two pools must have some common ancestor pool
(possibly the root pool --- is there a root pool?), and ENDURING must
be an immediate child of that ancestor pool. */
void apr_free_pool_after (apr_pool_t *enduring, apr_pool_t *transient);
Then you'd always ensure the cache pool was going to be freed after
whatever pool was containing the svn_fs_t.
It just seems like anyone trying to implement some sort of cache for
sharing is going to run into these problems.
I'm not sure whether this solution is minimal or graceful. :)
Re: Inexcusable BDB upgrade triple blunder
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 2/27/06, Branko Čibej <br...@xbc.nu> wrote:
> So ... any bright ideas?
How about the following hare-brained scheme:
Have the BDB env handles and filesystem objects both store pointers to
each other, so the first one that has a pool cleanup fire can NULL out
the pointers that refer to it? That way the second one to fire can't
get back to the free'd memory.
-garrett
Re: Inexcusable BDB upgrade triple blunder
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 2/28/06, Branko Čibej <br...@xbc.nu> wrote:
>
> As I said in an earlier post, I'd have to check if the cache is there
> every time the environment handle is used, not just in the svn_fs_t
> cleanup code. Can be done, but it's messy.
Why? We know that the only time the environment handle would ever disappear
is if the pool cleanup code is being invoked. If we lost a global pool,
it's time to go away... -- justin
Re: Inexcusable BDB upgrade triple blunder
Posted by Branko Čibej <br...@xbc.nu>.
Greg Hudson wrote:
> On Wed, 2006-03-01 at 00:16 +0100, Branko Čibej wrote:
>
>>> Here's my brilliant idea: set bdb_cache to NULL in a pool cleanup for
>>> bdb_cache_pool. In the svn_fs_destroy handler, check if bdb_cache is
>>> NULL and don't touch the underlying environment handle if so.
>>>
>
>
>> Yes, I was thinking along those lines. Except that it means we can't
>> allocate the environment handles from pools, because then their lifetime
>> will by definition be shorter than the cache's.
>>
>
> Eh? I don't understand.
>
> apr_terminate invoked
> Environment handle pools are cleaned up
> Cache pool is cleaned up --> bdb_cache set to NULL
> FS objects are cleaned up, but don't touch environment handles
>
> What's the problem?
>
As I said in an earlier post, I'd have to check if the cache is there
every time the environment handle is used, not just in the svn_fs_t
cleanup code. Can be done, but it's messy.
Anyway, thanks for the suggestions, everyone. I'll think about them a
bit and decide what to do.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Greg Hudson <gh...@MIT.EDU>.
On Wed, 2006-03-01 at 00:16 +0100, Branko Čibej wrote:
> > Here's my brilliant idea: set bdb_cache to NULL in a pool cleanup for
> > bdb_cache_pool. In the svn_fs_destroy handler, check if bdb_cache is
> > NULL and don't touch the underlying environment handle if so.
> Yes, I was thinking along those lines. Except that it means we can't
> allocate the environment handles from pools, because then their lifetime
> will by definition be shorter than the cache's.
Eh? I don't understand.
apr_terminate invoked
Environment handle pools are cleaned up
Cache pool is cleaned up --> bdb_cache set to NULL
FS objects are cleaned up, but don't touch environment handles
What's the problem?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Branko Čibej <br...@xbc.nu>.
Greg Hudson wrote:
> On Tue, 2006-02-28 at 06:47 +0100, Branko Čibej wrote:
>
>> The consequence is that, when we hit apr_terminate, the cache's pool can
>> be destroyed before the pool that contains the svn_fs_t that refers to
>> the cache; that's because APR destroys its (global) pools in LIFO order.
>> Unfortunately that means that during destruction of the svn_fs_t, we try
>> to access memory that's already been freed.
>>
>
> Here's my brilliant idea: set bdb_cache to NULL in a pool cleanup for
> bdb_cache_pool. In the svn_fs_destroy handler, check if bdb_cache is
> NULL and don't touch the underlying environment handle if so.
>
Yes, I was thinking along those lines. Except that it means we can't
allocate the environment handles from pools, because then their lifetime
will by definition be shorter than the cache's.
So it looks like a mixture of heap and pool allocations will be the way
to go after all ...
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Greg Hudson <gh...@MIT.EDU>.
On Tue, 2006-02-28 at 06:47 +0100, Branko Čibej wrote:
> The consequence is that, when we hit apr_terminate, the cache's pool can
> be destroyed before the pool that contains the svn_fs_t that refers to
> the cache; that's because APR destroys its (global) pools in LIFO order.
> Unfortunately that means that during destruction of the svn_fs_t, we try
> to access memory that's already been freed.
Here's my brilliant idea: set bdb_cache to NULL in a pool cleanup for
bdb_cache_pool. In the svn_fs_destroy handler, check if bdb_cache is
NULL and don't touch the underlying environment handle if so.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Branko Čibej <br...@xbc.nu>.
kfogel@collab.net wrote:
> Branko Čibej <br...@xbc.nu> writes:
>
>> Manuzhai wrote:
>>
>>>> What makes me angry about this is the same thing that made me angry
>>>> the last time I tripped over a rather similar database-recovery botch.
>>>>
>>> Well, if you want to prevent it from happening another time, you
>>> might just want to hop onto the fsfs bandwagon. It's become the
>>> default for 1.2, and for a reason - seems much more stable, no more
>>> db-recovery.
>>>
>> Hm, or the 1.3.(1?) bandwagon with bdb-4.4 -- no more db-recovery
>> there, either. :)
>>
>
> Speaking of which... where do we stand with 1.3.1 and BDB, Brane? Is
> the r18144-etc entry in STATUS ready for review and voting, or are any
> other changes still coming in?
>
The state of the world is that I'm fighting a cold (or is it avian flu?)
that's got my brain even more stuffed up than usual, and I'd rather not
touch this until I'm reasonably certain that I'm back to my normal IQ
level :( higher than right now, in case there's any doubt, thanks :)
> For what it's worth, I got a call from Keith Bostic the other day
> (which I don't think he'd mind my reporting about in a public forum),
> basically saying that the acquisition by Oracle does not change
> anything -- Sleepycat remains available to help in any way they can
> with the SVN integration of BDB 4.4. It didn't sound like you were
> stuck on anything that needed consultation with Sleepycat, but I
> thought I'd mention it just in case.
>
No, I don't need any help from Sleepycat.
I would, however, appreciate some help from the list.
Here's the problem:
* We have a global cache of open BDB environment descriptors. This
cache is of course allocated from a (global) pool, and each
descriptor gets its own subpool. The cached descriptors are
reference-counted.
* Each svn_fs_t owns a handle to one of these descriptors. These
handles (actually, their allocators and pool cleanups) manage the
descriptor reference counts.
So far so good. Everything works beautifully, no memory leaks anywhere.
Sheer paradise ...
... except for one nasty problem. The global pool for the cache can be
created *after* the first svn_fs_t is allocated (from a different pool).
Because we have no requirement about library initialization order in
1.x, we can only create the cache when it's first needed, not, say, just
after apr_initialize.
The consequence is that, when we hit apr_terminate, the cache's pool can
be destroyed before the pool that contains the svn_fs_t that refers to
the cache; that's because APR destroys its (global) pools in LIFO order.
Unfortunately that means that during destruction of the svn_fs_t, we try
to access memory that's already been freed.
I've pretty much convinced myself that this can only happen during
apr_terminate, but that's not much help, because it can still
potentially cause a crash (or worse).
I can't change the pool cleanup order short of a) hacking the pool
structure directly (eek!), or b) requiring that svn_fs_initialize be
called right after apr_initialize (ook ... er, that is, impossible).
I've considered using malloc to allocate the descriptors, but i'd still
need a pool per descriptor for open file handles, utf8->native
translation of database paths, etc.
I'm sure that, with all the brainpower on this list, someone will come
up with a trivially elegant solution to this problem.
So ... any bright ideas?
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by "Ronald V. Simmons" <Va...@TheSimmonses.Net>.
oops! sorry about this, responding to another message altogether and
accidentally hit the send button.
rvs
On Feb 27, 2006, at 7:07 PM, Ronald V. Simmons wrote:
> its alphabetical by first and last name.
>
> rvs
>
> On Feb 27, 2006, at 2:00 PM, kfogel@collab.net wrote:
>
>> Branko Čibej <br...@xbc.nu> writes:
>>> Manuzhai wrote:
>>>>> What makes me angry about this is the same thing that made me
>>>>> angry
>>>>> the last time I tripped over a rather similar database-recovery
>>>>> botch.
>>>>
>>>> Well, if you want to prevent it from happening another time, you
>>>> might just want to hop onto the fsfs bandwagon. It's become the
>>>> default for 1.2, and for a reason - seems much more stable, no more
>>>> db-recovery.
>>>
>>> Hm, or the 1.3.(1?) bandwagon with bdb-4.4 -- no more db-recovery
>>> there, either. :)
>>
>> Speaking of which... where do we stand with 1.3.1 and BDB, Brane? Is
>> the r18144-etc entry in STATUS ready for review and voting, or are
>> any
>> other changes still coming in?
>>
>> For what it's worth, I got a call from Keith Bostic the other day
>> (which I don't think he'd mind my reporting about in a public forum),
>> basically saying that the acquisition by Oracle does not change
>> anything -- Sleepycat remains available to help in any way they can
>> with the SVN integration of BDB 4.4. It didn't sound like you were
>> stuck on anything that needed consultation with Sleepycat, but I
>> thought I'd mention it just in case.
>>
>> -Karl
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: dev-help@subversion.tigris.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by "Ronald V. Simmons" <Va...@TheSimmonses.Net>.
its alphabetical by first and last name.
rvs
On Feb 27, 2006, at 2:00 PM, kfogel@collab.net wrote:
> Branko Čibej <br...@xbc.nu> writes:
>> Manuzhai wrote:
>>>> What makes me angry about this is the same thing that made me angry
>>>> the last time I tripped over a rather similar database-recovery
>>>> botch.
>>>
>>> Well, if you want to prevent it from happening another time, you
>>> might just want to hop onto the fsfs bandwagon. It's become the
>>> default for 1.2, and for a reason - seems much more stable, no more
>>> db-recovery.
>>
>> Hm, or the 1.3.(1?) bandwagon with bdb-4.4 -- no more db-recovery
>> there, either. :)
>
> Speaking of which... where do we stand with 1.3.1 and BDB, Brane? Is
> the r18144-etc entry in STATUS ready for review and voting, or are any
> other changes still coming in?
>
> For what it's worth, I got a call from Keith Bostic the other day
> (which I don't think he'd mind my reporting about in a public forum),
> basically saying that the acquisition by Oracle does not change
> anything -- Sleepycat remains available to help in any way they can
> with the SVN integration of BDB 4.4. It didn't sound like you were
> stuck on anything that needed consultation with Sleepycat, but I
> thought I'd mention it just in case.
>
> -Karl
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by kf...@collab.net.
Branko Čibej <br...@xbc.nu> writes:
> Manuzhai wrote:
> >> What makes me angry about this is the same thing that made me angry
> >> the last time I tripped over a rather similar database-recovery botch.
> >
> > Well, if you want to prevent it from happening another time, you
> > might just want to hop onto the fsfs bandwagon. It's become the
> > default for 1.2, and for a reason - seems much more stable, no more
> > db-recovery.
>
> Hm, or the 1.3.(1?) bandwagon with bdb-4.4 -- no more db-recovery
> there, either. :)
Speaking of which... where do we stand with 1.3.1 and BDB, Brane? Is
the r18144-etc entry in STATUS ready for review and voting, or are any
other changes still coming in?
For what it's worth, I got a call from Keith Bostic the other day
(which I don't think he'd mind my reporting about in a public forum),
basically saying that the acquisition by Oracle does not change
anything -- Sleepycat remains available to help in any way they can
with the SVN integration of BDB 4.4. It didn't sound like you were
stuck on anything that needed consultation with Sleepycat, but I
thought I'd mention it just in case.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Manuzhai <ma...@supaari.manuzhai.nl>.
> Hm, or the 1.3.(1?) bandwagon with bdb-4.4 -- no more db-recovery there,
> either. :)
But then that would involve another BDB-upgrade, Mr. ESR doesn't seem to
be a fan of those. ;)
Regards,
Manuzhai
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Branko Čibej <br...@xbc.nu>.
Manuzhai wrote:
>> What makes me angry about this is the same thing that made me angry
>> the last time I tripped over a rather similar database-recovery botch.
>
> Well, if you want to prevent it from happening another time, you might
> just want to hop onto the fsfs bandwagon. It's become the default for
> 1.2, and for a reason - seems much more stable, no more db-recovery.
Hm, or the 1.3.(1?) bandwagon with bdb-4.4 -- no more db-recovery there,
either. :)
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Manuzhai <ma...@supaari.manuzhai.nl>.
> What makes me angry about this is the same thing that made me angry
> the last time I tripped over a rather similar database-recovery botch.
Well, if you want to prevent it from happening another time, you might
just want to hop onto the fsfs bandwagon. It's become the default for
1.2, and for a reason - seems much more stable, no more db-recovery.
Regards,
Manuzhai
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Mark Phippard <ma...@softlanding.com>.
"Eric S. Raymond" <es...@thyrsus.com> wrote on 02/20/2006 02:02:18 AM:
> Max Bowsher <ma...@ukf.net>:
>
> > Oops. I see we really have screwed up the FAQ entry's background info.
> > There is no such function db_recover(), as it mentions.
> > - From what I can remember, the issue was actually that the response
of
> > BDB 4.3 to the invocation that Subversion has always used was
different
> > to the response of BDB 4.0/1/2. I will go and investigate the
situation,
> > and fix that misinformation.
>
> The FAQ author was hallucinating the existence of db_recover(), then;
> see my "on drugs" comment.
I do not have any desire to jump too far into this discussion as I have
virtually no BDB knowledge or experience. I just wanted to point out that
there is a db_recover.exe with the Win32 version of BDB. Further, my
recollection of this FAQ was that it was written originally for the Win32
version of Subversion as it started shipping with BDB 4.3 by default when
Subversion 1.2 was originally released.
I think part of the problem here was that this FAQ was originally written
for the Win32 user-base and was then not adequately maintained and updated
as more knowledge was revealed and as BDB started getting updated to the
newer revision in various *nix distros.
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by "Eric S. Raymond" <es...@thyrsus.com>.
Max Bowsher <ma...@ukf.net>:
> First: What is the point of self-declaring a message as a flame? It
> seems to me that the only thing this accomplishes is to deliberately
> incite anger in the recipients.
Any kind of arousal would be better than the torpor that seems to have had
the dev group in its grip on this issue for nearly three months. I'm not
in the habit of launching on people without a reason at least that good.
> Second: What happened to "don't claim you have found a bug unless you
> are very, very sure of your ground." and "Courtesy never hurts, and
> sometimes helps", as asserted in
> http://www.catb.org/~esr/faqs/smart-questions.html ?
Since the whole wretched mess pivots around a real and admitted bug,
the above is just defensive posturing and a waste of everybody's time.
> Oops. I see we really have screwed up the FAQ entry's background info.
> There is no such function db_recover(), as it mentions.
> - From what I can remember, the issue was actually that the response of
> BDB 4.3 to the invocation that Subversion has always used was different
> to the response of BDB 4.0/1/2. I will go and investigate the situation,
> and fix that misinformation.
The FAQ author was hallucinating the existence of db_recover(), then;
see my "on drugs" comment.
> It seems that previous efforts to use BDB 4.3 on this repository had
> created a 4.3-version log file.
Right. Did the FAQ entry observe that the initial failure that threw
the DB_VERSION error would likely leave the repo with a mixed bag of 4.2 and
4.3 logfiles in it, dooming the stated recovery algorithm to fail? Why...
no...it didn't.
(And that wasn't the only thing wrong. dbrecover appeared to be saying it
couldn't find any file with the expected name, which strongly suggests that
the invocation instructions for dbrecover were broken in the first place.)
What makes me angry about this is the same thing that made me angry
the last time I tripped over a rather similar database-recovery botch.
In both cases your FAQ entries were either uninformative or plain
*wrong*, and your stated recovery procedures brittle to the point of
uselessness. Twice, I've seen this group behave as though if you
write about these problems dismissively enough, they'll never actually
bite anyone.
There is no question that you guys in the dev group are bright and
capable enough to write recovery procedures and FAQs that actually
*work* -- therefore, your failure to do so can only be down to
carelessness, laziness, or arrogance. When you exhibit carelessness,
laziness or arrogance, you deserve to be flamed and flamed is exactly
what you will get.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Max Bowsher <ma...@ukf.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eric S. Raymond wrote:
> Once before I flamed the Subversion dev group over an unbelievable
> sequence of blunders, slipshod programming, and culpable
> obliviousness to the situation of actual users. Looks like it's time
> I have to do it again, and once again the botch combines a broken
> administrative procedure with pathetically inadequate documentation
> and an alleged recovery path that's a mirage.
Hello.
I have a couple of questions for you:
First: What is the point of self-declaring a message as a flame? It
seems to me that the only thing this accomplishes is to deliberately
incite anger in the recipients.
Second: What happened to "don't claim you have found a bug unless you
are very, very sure of your ground." and "Courtesy never hurts, and
sometimes helps", as asserted in
http://www.catb.org/~esr/faqs/smart-questions.html ?
> Yes, this means I've tripped over the 4.2->4.3 BDB upgrade problem.
> My symptoms:
>
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///home/esr/WWW/shipper/SVN/trunk/README'
> svn: Berkeley DB error for filesystem /home/esr/WWW/shipper/SVN/db while opening environment:
> DB_VERSION_MISMATCH: Database environment version mismatch
> svn: bdb: Program version 4.3 doesn't match environment version
>
> First blunder: screwing up db_recover() so a current svnadmin can't
> be used to upgrade the repository. But that would have been OK,
> except for...
Oops. I see we really have screwed up the FAQ entry's background info.
There is no such function db_recover(), as it mentions.
- From what I can remember, the issue was actually that the response of
BDB 4.3 to the invocation that Subversion has always used was different
to the response of BDB 4.0/1/2. I will go and investigate the situation,
and fix that misinformation.
> Second blunder: the FAQ answer. Fix it with an older version of
> svnadmin? Sounds like a peachy idea -- until the svnadmin run fails
> because it doesn't see the right version of the SVN repo shared
> libraries to dynamic-link to. A 100% predictable roadblock about
> which the FAQ entry says *nothing*.
No, this is neither 100% predictable, nor is it a significant roadblock.
If your older version of svnadmin uses shared libraries, then you should
install the appropriate versions. Presumably, they are available through
exactly the same means as the older version of svnadmin itself was.
> Oh, and by the way, there's that marvelously vague instruction to
> 'make a backup'. Why?
In case something unexpected goes wrong.
> With what?
Anything you like. 'cp' or 'tar', for instance.
> And how does one tell if one needs to *use* the backup?
The whole point of having a backup is to recover from _un_expected
circumstances.
> In general, this FAQ entry is so dizzyingly useless to anyone who
> doesn't inhabit the skull of a Subversion developer that one is left
> to wonder that kind of drugs the dolt who wrote it was on.
Vastly over-the-top ad-hominem attack, containing the grain of truth
that the author wasn't as thoroughly familiar with the issues as
would ideally be the case.
> Here, too, the lossage could easily have been contained -- by
> carrying links to downloadable statically linked svnadmin42 binaries
> for major platforms in the FAQ entry. But no. That would have made
> too much sense.
I'd like to point out that the Subversion project has _always_ made only
source-code releases, and has left the production of binaries up to
third parties. We have no control over what kinds of binaries they
produce. Certainly, we would be happy to append distro-specific notes to
the end of that FAQ entry if asked.
> Third blunder: Instead, diligent Googling turned up a set of recovery
> instructions bypassing svnadmin and using the db* utilities. Except
> that when applied on the most commonly deployed Linux distribution
> (Fedora Core) the instructions don't actually, you know, *work* or
> anything. I'm referring to this:
>
> http://lists.alioth.debian.org/pipermail/pkg-subversion-maintainers/2005-November/000268.html
>
> Buoyed up by the naive confidence that a reply I found on the
> Subversion dev list itself might embody something resembling a clue,
> I did as it suggested and wrote a script, intending to donate it
> back to the project. Here it is:
>
> ------------------------------------------------------------------------------
> #!/bin/sh
> #
> # Upgrade a local SVN repo from BDB 4.2. Follows the instructions in
> # http://lists.alioth.debian.org/pipermail/pkg-subversion-maintainers/2005-November/000268.html
> #
> repo=$1
>
> db42_checkpoint -1 -h ${repo}/db
> db42_recover -h ${repo}/db
> db42_archive -d -h ${repo}/db
> rm ${repo}/db/__db.???
> ------------------------------------------------------------------------------
>
> Notice that I couldn't actually follow the instructions, because the
> db utility names weren't right.
Yes, Fedora and Debian use different ways of disambiguating versions of
db_ utilities. Given the recipe was presented in a Debian context,
naturally the Debian names were used.
> I fixed them, and ran the script, and got this:
>
> db_checkpoint: open: No such file or directory
> db_recover: Ignoring log file: SVN/db/log.0000000004: unsupported log version 10
> db_recover: Invalid log file: log.0000000004: Invalid argument
> db_recover: PANIC: Invalid argument
> db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
> db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
> db_archive: Ignoring log file: SVN/db/log.0000000004: unsupported log version 10
> db_archive: Invalid log file: log.0000000004: Invalid argument
> db_archive: PANIC: Invalid argument
> db_archive: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
> db_archive: open: DB_RUNRECOVERY: Fatal error, run database recovery
> rm: cannot remove `SVN/db/__db.???': No such file or directory
>
> And yes, I did check that the repo path was correct. (It pretty much
> has to be for the second error line to have been generated.)
It seems that previous efforts to use BDB 4.3 on this repository had
created a 4.3-version log file.
> But I should not have had to try writing a recovery script iun the
> first place. I can see by the date of the aforementioned posting
> that this bug has been a known problem for *three* *months*. That
> tells me there is zero excuse for there not to have been a fix script
> downloadable through the Subversion FAQ page and dated at least two
> and a half months ago.
And what exactly do you take the list of steps in the FAQ entry to be,
other than a script written out in English to encourage care in working
through it?
To the best of our knowledge that sequence of instructions *works*.
Something caused additional problems in your case, but in general, it works.
> What in the fleeping frack were you guys *thinking*? Or, more likely,
> not-thinking.
We're thinking that:
(1) We provide source releases only, and have _always_ recommended the
use of 'svnadmin dump' and 'svnadmin load' as the safest way to change
BDB versions.
(2) We provided a recipe that many people have had success with to
short-circuit the admittedly lengthy 'svnadmin dump/load' technique.
> It's guaranteed that this same problem is going to mug anyone who
> updates from the 1.1.4 stock on FC4 to 1.2.3. You've now left
> anybody who relied on your upgrade path with invisibly broken
> repositories and no way out for at least *eight* *weeks*.
If the Fedora Core packagers have allowed a silent upgrade across BDB
versions without any sort of notification or warning, then they have not
acted in the best interests of their users. Please redirect your rant.
We've provided a way out, which apparently didn't work smoothly for you.
I guess I'll extract the grain of bug-report from the inferno, and see
if I can reproduce the specific failure mode you've reported.
> That's inexcusable. Whoever is responsible for this triple-play of
> incompetence should be deeply ashamed. It reflects badly in the
> entire dev group.
To recap:
1a: We failed to spot that the *background info* about the 4.2/4.3
issues in the FAQ entry was incorrect.
1b: Regarding the underlying problem that _should_ have been described
there - when the behaviour of a library we use changed, we attempted to
document the problems caused.
2: We used the words "make a backup" in our FAQ where we might have left
less room for confusion by saying "make a copy, just in case anything
unexpected goes wrong".
3: Some instructions you found on the dev list failed to work for you,
possibly because of other attempts to upgrade you tried before trying them.
Well, point 1a certainly warrants an exclamation of "Oops!" from the dev
team, but since it was a fault in background info only, it's relatively
minor.
As for 1b, in hindsight, given the amount of people running into
problems, we would have been better off modifying the code to smooth
over the issue, rather that only documenting the issue.
Point 2 - Maybe we could rephrase that.
Point 3 - Commiserations, but not our fault.
Max Bowsher.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
iD8DBQFD+IdVfFNSmcDyxYARAn+FAKCz0dvBIMZJFzYxTInhyzn+bYP/KgCfWR51
e6PSTpdhjEFexEcilp5Th5s=
=wOyk
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by kf...@collab.net.
"Eric S. Raymond" <es...@thyrsus.com> writes:
> kfogel@collab.net <kf...@collab.net>:
> > After a message like that, I sort of expected a patch to our FAQ.
> > Do you have time to prepare one?
>
> Yes, but not the information needed to do it.
Okay. But based on reading your original message, and now the
responses, it looks like you have enough information to at least
improve the FAQ entry. For example, you now know that the vague
phrase "make a backup of the repository" means "use cp or something
similar".
Do Max Bowsher's changes of r18527 and r18525 address everything you
could currently address, or could you improve it more?
I'm not asking you for the patch as a show of form or something.
You've just had direct experience with the problem and the FAQ entry
that purported to solve it. I think you're in a better position to
improve the FAQ entry than I am (for one thing, I may be too familiar
with Subversion to see things from the right point of view!), and if
you could at least patch it up as much as you're able, and leave todo
notes indicating where the entry is insufficient/incorrect, that would
help a lot. We'd then have some fixes already done, and clear,
in-context guidance as to what fixes remain.
My principle problem with your flame mail is that the flamage was
distracting -- it wasted the time of those of us trying to get right
to the technical issues, because we had to wade through all that other
stuff. The rudeness was annoying, sure, but if the mail had been at
least concise, it wouldn't be such a chore to extract the useful bits
from it. I'm not saying that to insult you; I'm saying it in the
hopes that future mails will be more concise, and thus more effective
at what is presumably our shared goal.
Thanks,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Peter Samuelson <pe...@p12n.org>.
[Eric S. Raymond]
> kfogel@collab.net <kf...@collab.net>:
> > After a message like that, I sort of expected a patch to our FAQ.
> > Do you have time to prepare one?
>
> Yes, but not the information needed to do it.
My writeup for the Debian packaging should be at least within shouting
distance of factually correct.
http://svn.debian.org/wsvn/pkg-subversion/trunk/debian/README.db4.3?op=file
Perhaps that will give you enough background information to write a
useful FAQ entry.
Re: Inexcusable BDB upgrade triple blunder
Posted by "Eric S. Raymond" <es...@thyrsus.com>.
kfogel@collab.net <kf...@collab.net>:
> After a message like that, I sort of expected a patch to our FAQ.
> Do you have time to prepare one?
Yes, but not the information needed to do it.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by kf...@collab.net.
After a message like that, I sort of expected a patch to our FAQ.
Do you have time to prepare one?
Thanks,
-Karl
--
www.collab.net <> CollabNet | Distributed Development On Demand
"Eric S. Raymond" <es...@snark.thyrsus.com> writes:
> Once before I flamed the Subversion dev group over an unbelievable sequence of
> blunders, slipshod programming, and culpable obliviousness to the situation
> of actual users. Looks like it's time I have to do it again, and once again
> the botch combines a broken administrative procedure with pathetically
> inadequate documentation and an alleged recovery path that's a mirage.
>
> Yes, this means I've tripped over the 4.2->4.3 BDB upgrade problem.
> My symptoms:
>
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///home/esr/WWW/shipper/SVN/trunk/README'
> svn: Berkeley DB error for filesystem /home/esr/WWW/shipper/SVN/db while opening environment:
> DB_VERSION_MISMATCH: Database environment version mismatch
> svn: bdb: Program version 4.3 doesn't match environment version
>
> First blunder: screwing up db_recover() so a current svnadmin can't be
> used to upgrade the repository. But that would have been OK, except for...
>
> Second blunder: the FAQ answer. Fix it with an older version of
> svnadmin? Sounds like a peachy idea -- until the svnadmin run fails
> because it doesn't see the right version of the SVN repo shared libraries to
> dynamic-link to. A 100% predictable roadblock about which the
> FAQ entry says *nothing*.
>
> Oh, and by the way, there's that marvelously vague instruction to
> 'make a backup'. Why? With what? And how does one tell if one needs
> to *use* the backup? In general, this FAQ entry is so dizzyingly
> useless to anyone who doesn't inhabit the skull of a Subversion
> developer that one is left to wonder that kind of drugs the dolt who
> wrote it was on.
>
> Here, too, the lossage could easily have been contained -- by carrying
> links to downloadable statically linked svnadmin42 binaries for major
> platforms in the FAQ entry. But no. That would have made too much sense.
>
> Third blunder: Instead, diligent Googling turned up a set of recovery
> instructions bypassing svnadmin and using the db* utilities. Except
> that when applied on the most commonly deployed Linux distribution
> (Fedora Core) the instructions don't actually, you know, *work* or
> anything. I'm referring to this:
>
> http://lists.alioth.debian.org/pipermail/pkg-subversion-maintainers/2005-November/000268.html
>
> Buoyed up by the naive confidence that a reply I found on the
> Subversion dev list itself might embody something resembling a clue, I
> did as it suggested and wrote a script, intending to donate it back to
> the project. Here it is:
>
> ------------------------------------------------------------------------------
> #!/bin/sh
> #
> # Upgrade a local SVN repo from BDB 4.2. Follows the instructions in
> # http://lists.alioth.debian.org/pipermail/pkg-subversion-maintainers/2005-November/000268.html
> #
> repo=$1
>
> db42_checkpoint -1 -h ${repo}/db
> db42_recover -h ${repo}/db
> db42_archive -d -h ${repo}/db
> rm ${repo}/db/__db.???
> ------------------------------------------------------------------------------
>
> Notice that I couldn't actually follow the instructions, because the db utility
> names weren't right. I fixed them, and ran the script, and got this:
>
> db_checkpoint: open: No such file or directory
> db_recover: Ignoring log file: SVN/db/log.0000000004: unsupported log version 10
> db_recover: Invalid log file: log.0000000004: Invalid argument
> db_recover: PANIC: Invalid argument
> db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
> db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
> db_archive: Ignoring log file: SVN/db/log.0000000004: unsupported log version 10
> db_archive: Invalid log file: log.0000000004: Invalid argument
> db_archive: PANIC: Invalid argument
> db_archive: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
> db_archive: open: DB_RUNRECOVERY: Fatal error, run database recovery
> rm: cannot remove `SVN/db/__db.???': No such file or directory
>
> And yes, I did check that the repo path was correct. (It pretty much
> has to be for the second error line to have been generated.)
>
> But I should not have had to try writing a recovery script iun the
> first place. I can see by the date of the aforementioned posting that
> this bug has been a known problem for *three* *months*. That tells me
> there is zero excuse for there not to have been a fix script
> downloadable through the Subversion FAQ page and dated at least two
> and a half months ago.
>
> What in the fleeping frack were you guys *thinking*? Or, more likely,
> not-thinking. It's guaranteed that this same problem is going to mug
> anyone who updates from the 1.1.4 stock on FC4 to 1.2.3. You've now
> left anybody who relied on your upgrade path with invisibly broken
> repositories and no way out for at least *eight* *weeks*.
>
> That's inexcusable. Whoever is responsible for this triple-play of
> incompetence should be deeply ashamed. It reflects badly in the entire
> dev group.
> --
> <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
>
> In the absence of any evidence tending to show that possession
> or use of a 'shotgun having a barrel of less than eighteen inches
> in length' at this time has some reasonable relationship to the
> preservation or efficiency of a well regulated militia, we cannot
> say that the Second Amendment guarantees the right to keep and bear
> such an instrument. [...] The Militia comprised all males
> physically capable of acting in concert for the common defense.
> -- Majority Supreme Court opinion in "U.S. vs. Miller" (1939)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
--
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Inexcusable BDB upgrade triple blunder
Posted by Peter Samuelson <pe...@p12n.org>.
[Eric S. Raymond]
> Whoever is responsible for this triple-play of incompetence should be
> deeply ashamed. It reflects badly in the entire dev group.
Talk to the fedora packagers, I guess.[*] This sort of thing is exactly
why we have distributions. I'm sure they were aware of the upgrade
issues, since that's pretty fundamentally a part of software packaging.
They should have documented an upgrade procedure that works on their
platform, and arranged for admins to see it when they upgrade, however
that is done in fedora. Or stuck with db4.2, not that this is
necessarily convenient (if you use the system libaprutil, it dictates
your db version).
[*] Potential conflict of interest on this counter-flame: I'm the guy
who documented db4.2->4.3 for subversion in debian, and fussed
about it for a week or two before releasing it, afraid that I'd be
culpable for all manner of downtime or even data loss if I got it
wrong.
As for those who don't use software from their distribution - anyone
compiling his own software without heed to DB version upgrade issues
apparently hasn't been around very long. These things affect most
software that stores data in Berkeley DB.
Re: Inexcusable BDB upgrade triple blunder
Posted by David Ripton <dr...@ripton.net>.
On 2006.02.19 00:14:03 -0500, Eric S. Raymond wrote:
> Second blunder: the FAQ answer. Fix it with an older version of
> svnadmin? Sounds like a peachy idea -- until the svnadmin run fails
> because it doesn't see the right version of the SVN repo shared libraries to
> dynamic-link to. A 100% predictable roadblock about which the
> FAQ entry says *nothing*.
> Oh, and by the way, there's that marvelously vague instruction to
> 'make a backup'. Why? With what? And how does one tell if one needs
> to *use* the backup? In general, this FAQ entry is so dizzyingly
> useless to anyone who doesn't inhabit the skull of a Subversion
> developer that one is left to wonder that kind of drugs the dolt who
> wrote it was on.
I'm not a svn developer, yet I somehow managed.
Search the FAQ for "dump/load cycle". There's more than one way to
backup a svn repository, but "svnadmin dump" is the way to get a
completely version-independent one.
In theory, you only *need* to svnadmin dump / upgrade / svnadmin load
when the schema changes. Which hasn't happened since 1.0.
In practice, a dump/load cycle is easier than the kind of recovery you
attempted. Especially if you remembered to "svnadmin dump" *before* you
upgraded BDB, so you don't need to downgrade to do it. It may be slow
if the repository is big, though.
BDB is no longer the default backend in svn 1.2+, so this particular bit
of pain should mostly go away.
--
David Ripton dripton@ripton.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org