[erlang-questions] Corrupt database in mnesia

Kenneth Lundin <>
Tue Nov 3 08:21:31 CET 2009


If you have a previous log with size 150G I suppose you have run with
mensia overloaded for
quite some time.

What is your mnesia setup ? disk_copy tables or what?
How big entries in the tables?
The PREVIOUS.LOG is the transactions whose result is not yet written
into the tables. I.e
a backlog of things to do.
When you delete the PREVIOUS and LATEST you will miss all the
transactions not yet
reflected in the tables.

/Kenneth Erlang/OTP Ericsson

On Sun, Nov 1, 2009 at 10:07 PM, Yogish Baliga <> wrote:
> Hello all,
>  On our production box, I have seen mnesia getting corrupt once in a while. LATEST.LOG, PREVIOUS.LOG becomes 150G or so and 1st fragment of .DCL file reaches 6G or so. Restarting mnesia again will take forever to recover. But after deleting LATEST.LOG, PREVIOUS.LOG file and restarting mnesia will recover pretty fast and the data is intact in the database.
>  2 questions regarding this issue
>    1. What is causing the corruption of .LOG and .DCL files?
>    2. Why is that removing LATEST.LOG, PREVIOUS.LOG and restarting mnesia recovers pretty fast and data is not lost?
>    3. How to prevent this from happening again?
> Thanx,
> -- baliga
> "Point of view is worth 80 IQ points" --Alan Kay
> http://dudefrommangalore.blogspot.com/

More information about the erlang-questions mailing list