Bug 28103

GemStone/S

6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.2.x, 6.2, 6.1.6, 6.1.5, 6.1.x, 6.0.2, 6.0.1, 6.0

All

Tranlog full condition may cause stone to crash

Under some specific timing conditions, a tranlog full condition
can cause the stone to crash with a fatal stone error. While normally
the system is designed to pause when tranlogs are full, to allow space to be cleared or new tranlog directories to be added, there
are some points in the processing of a commit or other transaction
log entry where the code can not safely pause.  To preserve tranlog
integrity, the stone shuts down.  Since the tranlogs are full, it is
not possible to shut down cleanly.

Assuming tranlog space is made available, you can safely restart
the stone and allow it to recover.  There is no specific risk
associated with this bug, however, there are other bugs related to
tranlog full conditions, some of which do cause corruption; see
bugnotes for 30034 and 29024.   Other bugs associated with tranlog
full conditions are 28057, 29095, and 28082.

Workaround

None.  Avoid tranlog full conditions; a number of problems have been reported under this circumstance.


Last updated: 3/22/04