[Glass] GS 3.1.0.5: Fatal Internal Error, 5015, 15621, IO Error (RepRead Error)

[Dale Henrichs]

Pieter,

start with a fresh extent0.seaside.dbf and
before starting stone , add
   STN_TRAN_FULL_LOGGING=true;
   STN_TRAN_LOG_DEBUG_LEVEL=3;
to the stone config file .
Then after repository gets corrupted, run pageaudit and
if errors are similar , send us the extent and the tranlogs
for analysis (if possible).  Otherwise we will want you to
run some tranlog searches for us ...


On Mon, Jul 7, 2014 at 1:47 AM, <pieter at nagel.co.za> wrote:

> These fatal errors are still going on. so far it affects only development
> and staging repositories, so we can work around it, but we're growing
> increasingly nervous that it might hit production as well.
>
> To recap: repositories are becoming randomly corrupted into a state where
> any meaningfull Smalltalk evaluation causes topaz to dump errors like:
>
> RepRead Error hdr.pageId 0 != pageId
> 14635-----------------------------------------------------
> GemStone: Error         Fatal
> Please report to your GemStone Administrator:  Fatal Internal Error,
> 5015, 14635, IO Error
> Error Category: 231169 [Internal Fatal] Number: 4126  Arg Count: 3 Context
> : 20 exception : 20
> Arg 1: 40122
> Arg 2: 117082
> Arg 3: 20
>
> These bugs seem to be random. Rebuilding a clean development extent will
> fail one time and pass the next even though there are no changes to the
> code that is being filed in on top a virgin exten0.dbf in the two
> situations. Sometimes reboots inbetween seem to be needed for the problem
> to go away.
>
> Any advice for getting to the bottom of this?
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140707/c6320a4d/attachment.html>