To those of you following my locker saga, a recover gave me a
short-term solution to my problem, but eventually, it came back.
Specifically, our automatic build machine's query for changes seemed
to be what was clobbering it every time.
We were running up against some other issues that could be solved by
migrating to a fsfs back-end. So, I decided to do an emergency
migration. The whole migration seemed to be running relatively
smoothly -- TOO smoothly. Then, I encountered this little gem:
--------------------------
<<< Started new transaction, based on original revision 1046
* adding path : trunk/some folder ... done.
* adding path : trunk/some folder/some_file.zip ...File size
limit exceeded.
--------------------------
Now, I assume that it's complaining that the deltas file for revision
1046 is too big? But this is nuts! I've seen files over 20GB on this
hard drive before. There's 56GB of hard drive space available, so
it's not that there's insufficient hard drive space. Is this a
subversion-defined limit it's running up against?
I appreciate whoever can lend me some advice. My repository is
completely out of commission until I figure out what's going on. The
longer the repository is out of commission, the more you start hearing
artists start to suggest blasphemous notions like emailing files to
each other. :)
Tess
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 30 21:33:40 2005