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

Re: fsfs migration failure. File too large??

From: Brian Buesker <bbuesker_at_qualcomm.com>
Date: 2005-06-01 02:57:21 CEST

kfogel@collab.net wrote:

>Ben Collins-Sussman <sussman@collab.net> writes:
>>>If this is a real problem, I would suggest a warning in the release
>>So far, nobody's reported a problem.
>Someone would have to commit >2GB worth of *differences* in a single
>commit. It could happen -- and probably will, eventually -- so
>perhaps a mention in the release notes or FAQ would be a good idea.
>However, it's not as much of a showstopper as it might at first sound
Actually, I did run into this limitation a while back. We're storing
RPMs in a repository to allow us to roll our own Fedora Core releases
which include various updates. The RPMs are fetched via HTTP during the
install (where the URLs are actually ones in our repository). There were
a lot of updated RPMs when we rolled a release. Initially we were using
BDB, so when we tried to switch to FSFS, the load failed because of this
exact problem. I wound up just writing a quick perl script to split the
large revisions into separate dump files, and then doing the load with
those. It was somewhat of a hack, but it got the job done for the

Now we are just careful when adding new RPMs that we don't commit too
much in a single rev.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 1 02:59:13 2005

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

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