On Thu, Apr 17, 2014 at 10:12 AM, Rich Neswold <rich.nesw...@gmail.com> wrote: > On Wed, Apr 16, 2014 at 3:40 PM, Rich Neswold <rich.nesw...@gmail.com> wrote: >> It would be nice if fossil would break the "pull" into smaller >> transactions which contain valid timeline commits so, if there's a >> database timeout, the next time I try to "pull" it can continue where >> it left off. > > The first few times that my "pull"s failed, there was no obvious > change to the timeline so I assumed none of the data was being saved. > After the last timeout, however, there were some new entries from the > NetBSD project. So maybe new pulls start were the previous left off > after all.
Although syncs/pulls appear to make progress, even when a failure occurs, I'd still like to see a "fossil pull" breaking the request into multiple smaller transactions. The "one transaction for the entire request" doesn't scale at all. My main NetBSD fossil repo is 11G. I want to keep a copy on another machine so my local changes are stored in more than one location. Last night, my backup was 2G (because I hadn't sync-ed in a while) so I started a "fossil pull" and then went home. This morning, the pull was aborted by a "signal 2" and my local directory showed the following: [~/repo]$ ls -l total 351919880 -rw-r--r-- 1 neswold 2335277056 May 1 16:03 netbsd.fossil -rw-r--r-- 1 neswold 9273344 May 2 09:37 netbsd.fossil-shm -rw-r--r-- 1 neswold 177838427024 May 2 06:32 netbsd.fossil-wal That's right, my write-ahead file is 177 GB (16x the expected size of the final repository!) I'm doing a "fossil sqlite" and it's slowly trying to apply the transaction, but I really don't have any hope it will succeed -- I'm just curious what it will do. More than likely, I'll delete this repo and clone it again. There have to be points during a sync/pull that the target repository is in a stable, consistent state. The transaction can be committed and a new one started. Or maybe add a command-line option to pull/sync which lets the user select how many artifacts to pull over and then the user can run the command multiple times until nothing is left to transfer. -- Rich _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
