On Mon, Nov 19, 2012 at 9:22 AM, Stefan Bellon <[email protected]> wrote:
> On Mon, 19 Nov, Richard Hipp wrote: > > > Clearly I've overlooked something. If you can give me some idea of > > what is missing, I'll fix it. > > I found out what is causing this: I had a log file of over 4 GB size > (4376612120 bytes to be precise) in one of the sub directories. > Removing that file made the whole thing work. > > So, does this mean fossil has a maximum file size and files larger than > that cannot be committed? > Fossil compresses files using zlib (and delta compression if other similar files are available) and stores the result as an SQLite BLOB. The maximum size of an SQLite BLOB is 1GiB. So, unless the 4GiB file compresses well, it is not a candidate for being stored in an Fossil repository. You might have run into an integer overflow situation rather than an oversized BLOB. You should have gotten a better error message if there had been an SQLite failure. > > Greetings, > Stefan > > -- > Stefan Bellon > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
