Re: [Sks-devel] SKS PTree possible corruption?

[Yaron Minsky]

The latest patch (patch-11) in my TLA archives should eliminate those
spurious sigalarms.

Yaron

On Wed, 14 Jul 2004 10:33:19 +0200, Dinko Korunic <address@hidden> wrote:
> On Tue, Jul 13, 2004 at 09:32:22PM -0400, Yaron Minsky wrote:
> > Hmm.  This is a rather odd outcome.  I'd be curious as to which OS
> > you're running on, because as I understand unix semantics, the error
> 
> Actually, Sun Solaris 9 [SunOS xxx 5.9 Generic_112233-12 sun4u sparc] on
> UltraSparc processor [specifically, Sun Fire with two 1GHz CPU].
> 
> > alarm, and so that should really be that.  Why sigalarm is going off I
> > can't really fathom.
> 
> Yeps, code seems clear, as far as I can tell... but I don't do OCAML :/
> Could it be OCAML/Solaris issue?
> 
> > In any case, I have some workarounds in mind that might fix it.  But
> > before we go down that route, I'ld like to get some more information
> > as to what platform you're running on.
> 
> ACK. Tell me if you need any more info, or some tests to be run.
> 
> > Another thing worth noting is that the "PTree may be corrupted"
> > message is too alarmist.  What may be corrupted is the in-memory copy
> > of the PTree.  Since the transaction in question is aborted, there
> > should be no problem with the on-disk PTree, and so there should be no
> > need for rebuilding the PTree database.
> 
> Probably - however, I tried to ignore the message. As a result, those
> breakups tended to happen more and more often [sad, but true] and
> reconciliation process [db recon] was dying quite often.
> 
> Thanks for your time, BTW.
> 
> 
> 
> --
> |  |--.----.-----. Dinko 'kreator' Korunic       #include <stddisclaimer.h>
> |    <|   _|  -__| http://www.srce.hr/~kreator/ | http://kre.deviantart.com
> |__|__|__| |_____| PGP:0xEA160D0B | IRC:kre | ICQ:16965294 | AIM:kreatorMoo
>