Hi!
If it's not an already known and/or fixed misfeature, I would like to
report a problem with the 2GB limit of the FSFS filesystem. I tried both
1.1.4 from Debian stable as well as the 1.2.3 from backports.org and both
versions freak out when the rev file hits the 2GB limit during the
transaction (on ReiserFS, which doesn't have the 2GB limit itself).
Little background - I tried to test the SVN a bit before putting it in
production so I took few of our CVS modules and tried to import them
into SVN. One of the modules was about 8GB of data assets in about 20000
files, which makes suitable test bed.
The performance with DB filesystem was terrible, the commit took more than
2 hours, while the CVS is able to tag (i.e., read and write) the entire
module in about 20 minutes). Not to mention that I got the database wedged
in almost no time (just issuing lstxns during a running commit), which is
something I can't allow to happen in production. Also I wasn't really
comfortable with the idea of having single binary >8GB file holding all of
our valuable files...
So I tried to redump the repository to fsfs, but it crashed without any
error message when the rev file in the transaction subdir hit the 2GB
limit. Well, I simply deleted everything and did a new commit, this time
in chunks smaller than 2GB. This time it seems to work fine and gives us a
reasonable performance, we will see how it turns out once the history
starts to build up.
The 2GB limit is not an issue for us during the normal use in most cases,
but if someone has time it would be nice to get it fixed before someone
else burns himself due this problem.
Regards,
Patrik Rak
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 13 12:23:58 2005