[Sugar-devel] RFH - Journal corruption reports fom 8.2.1

[Jim Simmons]

Martin,

For what it's worth, I've experienced this running the Sugar test
environment in both Fedora 10 and 11.  It would not seem to be
specific to .82.  The way to reproduce the problem is to run the Sugar
environment in Xephyr (sugar-emulator).  Do some stuff, then instead
of shutting down cleanly click on the "close" button on the Xephyr
window.  That will close your Sugar session and practically guarantee
that the next time you open it your Sugar Journal will be empty.  I
regret to say that I've done this a few times.

James Simmons


> Date: Thu, 20 Aug 2009 18:56:17 +0200
> From: Martin Langhoff <martin.langhoff at gmail.com>
> Subject: [Sugar-devel] RFH - Journal corruption reports fom 8.2.1
>        users in Uy
> To: OLPC Devel <devel at lists.laptop.org>,        Sugar-dev
>        <Sugar-devel at lists.sugarlabs.org>
> Message-ID:
>        <46a038f90908200956h436459f3j9fa7b29bb111d130 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On olpc-sur we're seeing reports of "my journal contents disappeared
> after reboot". (Thread starts at
> http://lists.laptop.org/pipermail/olpc-sur/2009-August/004177.html )
>
> This reminds me a lot of the issues we saw earlier in development of
> what became 8.2.x -- if for any reason Sugar doesn't like the Journal
> contents or indexes, it moves the 'datastore' directory aside, and
> starts anew.
>
> That's my hunch, and I am hoping to hear confirmation from the users
> reporting the problem.
>
> Two pleas for help
>
>  - A sugar activity that does some data-recovery and freeing up the space.
>
> The good news is that we have a json file with the metadata for each
> Journal entry, so we can either load it back into the Journal (mstone
> had published a cli script that exports/imports to the Journal?) or
> create Journal Entry Bundles and save them to a USB stick.
>
> I suspect the JEB path might help users more -- if the Journal is
> choking on some specific metadata, a script that reloads it all in one
> go will make it choke again. Having files as JEBs allows step-by-step
> attempts.
>
>  - Diagnosis.
>
> If it's something we can pin down, it'll be great to have a fix! This
> will surely involve getting in touch with teachers on olpc-sur.
>
> cheers,
>
>
>
> m
> --
>  martin.langhoff at gmail.com
>  martin at laptop.org -- School Server Architect
>  - ask interesting questions
>  - don't get distracted with shiny stuff  - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff