From: Doug B. <dou...@gm...> - 2011-02-03 14:27:48
|
On Thu, Feb 3, 2011 at 8:50 AM, Benny Malengier <ben...@gm...> wrote: > > > 2011/2/3 Benny Malengier <ben...@gm...> >> >> >> 2011/2/3 Peter Landgren <pet...@te...> >>> >>> <snip> >>> > > The repair button is not active. Greyed out. >>> > >>> > This is not at all how it should be. >>> > If you have it again, eg with database grampsdb/abcdeg take a backup: >>> > cp grampsdb/abcdeg grampsdb/mytest >>> > Then in mytest, remove the backup database tables. Then run recovery >>> > tool >>> > on it: >>> > >>> > http://gramps-project.org/wiki/index.php?title=Recover_corrupted_family_tre >>> > e#Family_Tree_corruption >>> Now I had the db_recover to work in the correct directory. No errors >>> reported. >>> When I started Gramps, I saw I had only lost the last new person. >>> >>> Note, I have included self.env.log_flush() this time. >>> >>> >>> > You really should only loose the last commit, or something is going on >>> > that >>> > is really strange. Yes, we set the nosync flag now, but that means the >>> > OS >>> > is responsible for flushing to the disk. Is it possible your OS is not >>> > doing that? Do you write to flash memory? >>> > If it is not flushed, then it might become too large, and hence >>> > suddenly >>> > crash. >>> > >>> > Perhaps you can test like this: >>> > Open Gramps and open a terminal in the database directory >>> > Do some changes in Gramps and see if the timestamp in the database >>> > directory on change of the db tables is the time you did the change in >>> > gramps, or the time at which you do >>> > ls -all >>> > in that directory. >>> I see only time stamp changes in the log.000.. file and undo.db. >>> >> >> Yes, >> I see the same in trunk. When I use xkill to kill Gramps, and restart, my >> last change is gone, which it should not be. >> So we do something wrong. If you have time to test the released version of >> Gramps to do this, then please do, that does not use this change. > > If I remove the sync setting in trunk, I still loose everything, which is > not as it should be. All db files also have a new timestamp, while I only > changed a person name. It seems there is some automatic recover going on. > > This will need some investigating. > However, it is not related to your original crash, it just explains why > everything is gone. It is a pity viewvc does not work on sourceforge now, I > was used to use it to investigate problems. I remember Doug or somebody else > changed the cleanup of log settings on startup, that might also be a factor. > And I might have changed the automatic recovery flag. I made a change so that the logs would be cleaned up. But I really have no understanding of BSDDB, logs, recovery, etc. so I'm glad to see Benny going through this with a fine-toothed comb. -Doug > Benny > >> >>> >>> /Peter >> > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |