I have verified this a number of times, so it should be easily reproducible.
On client/server running 1.1.3 (bdb):
1) dump the full existing repository with svnadmin dump, dump is successful,
resulting file is 7.2GB
2) create a new repository with svnadmin create --fs-type bdb
3) load the dumpfle from step#1 with svnadmin load into new repository, load is
The above steps helps prove that the dumpfile is valid, and the load works
under 1.1.3, so no OS 2GB file limitations exist.
Now try with 1.2.1
4) upgrade server to 1.2.1
5) create a new repository with svnadmin create --fs-type bdb
6) load the dumpfile from step #1 with svnadmin load into the new repository
The load fails consistently at the 2GB barrier:
svnadmin: Berkeley DB error for filesystem d:/svn121/repo/db
while clearing string:
svnadmin: bdb: seek: 2206695424 0 2: Input/output error
svnadmin: bdb: ftruncate: 2206695424: Input/output error
This looks like a classic 2GB barrier issue. Steps #1-3 above show that it
loads fine under 1.1.3 on the same machine with the same OS. So it points to
an issue with 1.2.1 (I also tried with 1.2.0 and had the same problem).
If my understanding is correct, APR can not be at fault since this is not fsfs,
and it would have to be something with bdb. Perhaps the 1.2.1 win32 bdb was
built incorrectly (without largefile support), or was somehow linked in wrong?
Or a new issue with bdb 4.3?
Another user, Denis Cornehl, reported this same issue on 6/8/2005, and it was
left as unresolved. I believe he upgraded his bdb in-place, and that seemed to
be okay as a workaround, but he was never able to do a successful svnadmin
load. I could do the same workaround, but would much prefer the svnadmin load,
as it gives the confidence that the dumpfile loads cleanly, and also fully
utilizes the new xdelta algorithm.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Jul 27 01:43:18 2005