On Tue, Sep 6, 2011 at 7:42 PM, Matt Welland <[email protected]> wrote:
> I am continuing to test the limits of fossil and I've run into an > interesting case where I can't merge. I'd like to know how I could recover > from this. Note, this is from running the scripts (two in parallel) that I > put at :http://chiselapp.com/user/kiatoa/repository/testfossil with more > and larger files. The files are around 1-2 meg in size and the total data is > 1.2 Gig over 70 files. One file (the problem file) is 1G in size, probably > due to a bug in my test scripts. > The error occurs when Fossil tries to save the old content of the file as a BLOB in the UNDO table, so that it can undo the merge (restoring the original content of the file) if you later ask it too. Apparently I have the BLOB size limit set at 1GiB. > > Note 1. Stats from the repository are at the bottom of this email. > Note 2. I do not necessarily consider this a concern over performance with > fossil but I do want to understand what it means. > Note 3. "Delete or modify the offending file" is a fine answer but I'm > interested in hearing other ideas and views. > > chlr11723> fossil leaves > === 2011-09-06 === > 16:45:17 [e343a05970] *CURRENT* Manually syncing (user: mrwellan tags: > trunk) > 16:43:48 [700fc9b91b] Manually resyncing (user: mrwellan tags: trunk) > chlr11723> fossil merge 700fc9b91b > MERGE files/aa > MERGE files/ab > ***** 1 merge conflicts in files/ab > MERGE files/ac > ***** 1 merge conflicts in files/ac > MERGE files/ad > ***** 1 merge conflicts in files/ad > MERGE files/ae > MERGE files/af > MERGE files/ag > ***** 2 merge conflicts in files/ag > MERGE files/ah > MERGE files/ba > MERGE files/bb > MERGE files/bc > MERGE files/bd > fossil: error code 18: statement aborts at 9: [INSERT OR IGNORE INTO > undo(pathname,redoflag,existsflag,isExe,content) > VALUES('files/bd',0,1,0,:c)] string or blob too big > fossil: SQL error: string or blob too big > > If you have recently updated your fossil executable, you might > need to run "fossil all rebuild" to bring the repository > schemas up to date. > Rolling back prior filesystem changes... > UNDO files/aa > UNDO files/ab > UNDO files/ac > UNDO files/ad > UNDO files/ae > UNDO files/af > UNDO files/ag > UNDO files/ah > UNDO files/ba > UNDO files/bb > UNDO files/bc > fossil: SQLITE_BUSY: statement aborts at 2: [ROLLBACK] cannot rollback > transaction - SQL statements in progress > chlr11723> > > ============stats============= > Repository Size: 558905344 bytes Number Of Artifacts: 197747 (stored as > 4863 full text and 192884 delta blobs) Uncompressed Artifact Size: 690049 > bytes average, 1070741214 bytes max, 136454435349 bytes total > Compression Ratio: 244:1 Number Of Check-ins: 119289 Number Of Files: 239 > Number Of Wiki Pages: 0 Number Of Tickets: 0 Duration Of Project: 6 days > or approximately 0.02 years Project > ID:549128601262c7f7d8110788aee02608db3feb8b > Server ID: e73c5cb7f5bafb88ce4b9760ed635d36fc89b9b7 Fossil Version:2011-05-12 > 14:56:52 [d8221b9863] (gcc-4.2.2) > SQLite Version: 2011-04-27 19:54:44 [f55156c519] (3.7.6.1) Database > Stats:545806 pages, 1024 bytes/page, 21776 free pages, UTF-8, wal mode > > > _______________________________________________ > 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
