Jay Cornwall wrote:
> I'm using BDB 4.2.52, as mentioned in my first post. The server is
> running on RedHat Enterprise Linux 3.0 ES which comes with BDB 4.1.x by
> default; I ensure Subversion uses the correct DB library (installed into
> /usr/local/db) on compilation, and I've checked that it (and Apache)
> link to the correct version with ldd.
Judging from your error description it seems unlikely to be your fault.
Interestingly enough, the error message (about some memory page being
empty/corrupted) sounds suspiciously like something that pops up on the
PostgreSQL lists from time to time, where similar symptoms lead to
database corruption 'out of the blue'. As far as I can remember from those
threads the only common thing in all cases was that they happened on RH
Enterprise. This really sounds like some kernel/virtual memory/buffer
cache/VFS/ext3/driver problem where pages/blocks are not or not fully
written to disk. I know I occasionally had some of these under 2.4.x
(SuSE, not RH) when I still used it.
I really do not want to dis RH but personally I wouldn't touch their
transmogrified 2.4/2.6 Frankenkernel with the proverbial pitchfork (the
_regular_ kernel changelogs are scary enough). Have you considered trying
another kernel, e.g. vanilla 2.6.8? If that's not an option you could try
an fsfs repository when 1.1.1 comes out. After all it can't get worse.. :-}
Of course, all that being said, it's likely that in a few minutes someone
else will claim they've been running massive bdb repos on RHEL for ages
without any problems. All I know is that my company's >10GB repo has been
working flawlessly ever since it was put into production almost two years
ago, and survived migrations from RH7 and SuSE9 to Gentoo without any
hiccups at all.
Holger
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 18 01:48:15 2004