cache coherency fault, page in allocatedPagesTemp already free

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

cache coherency fault, page in allocatedPagesTemp already free

GLASS mailing list
Hi -

I have a 3.5.0 stone on Ubuntu 18.04 that failed to shut down properly because it ran out of space.  Through system.conf I limited the stone to 46.7GB.  After changing the limit to 48.5GB it still wont start, starts a gdb process, and gives the attached log.  



What should I do to fix it?


Thanks


Paul



_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass

cmsup35.log (51K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: cache coherency fault, page in allocatedPagesTemp already free

GLASS mailing list
Hi Paul,

From the stack it appears your extent is corrupted.  You should restore from backup and replay tranlogs. You could also try starting the stone using the 3.5.4 executables but I doubt that will make any difference.

Norm


On 10/25/2020 5:14 PM, PAUL DEBRUICKER via Glass wrote:
Hi - 

I have a 3.5.0 stone on Ubuntu 18.04 that failed to shut down properly because it ran out of space.  Through system.conf I limited the stone to 46.7GB.  After changing the limit to 48.5GB it still wont start, starts a gdb process, and gives the attached log.  



What should I do to fix it? 


Thanks


Paul



_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass


_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass
Reply | Threaded
Open this post in threaded view
|

Re: cache coherency fault, page in allocatedPagesTemp already free

GLASS mailing list
Ok thanks!


GLASS mailing list wrote

> Hi Paul,
>
>  From the stack it appears your extent is corrupted.  You should restore
> from backup and replay tranlogs. You could also try starting the stone
> using the 3.5.4 executables but I doubt that will make any difference.
>
> Norm
>
>
> On 10/25/2020 5:14 PM, PAUL DEBRUICKER via Glass wrote:
>> Hi -
>>
>> I have a 3.5.0 stone on Ubuntu 18.04 that failed to shut down properly
>> because it ran out of space.  Through system.conf I limited the stone to
>> 46.7GB.  After changing the limit to 48.5GB it still wont start, starts a
>> gdb process, and gives the attached log.
>>
>>
>>
>> What should I do to fix it?
>>
>>
>> Thanks
>>
>>
>> Paul
>>
>>
>>
>> _______________________________________________
>> Glass mailing list
>>

> Glass@.gemtalksystems

>> https://lists.gemtalksystems.com/mailman/listinfo/glass
>
>
> _______________________________________________
> Glass mailing list

> Glass@.gemtalksystems

> https://lists.gemtalksystems.com/mailman/listinfo/glass





--
Sent from: http://forum.world.st/GLASS-f1460844.html
_______________________________________________
Glass mailing list
[hidden email]
https://lists.gemtalksystems.com/mailman/listinfo/glass