Hi all,

The subject says it all.

This occurs during a gbak on FB 1.5.3.4870 running on a debian system
2.6.16 kernel, classic server configuration.

The gbak fails, but, none of the users encounter an error, and there are
137 connections currently to this database. This problem goes away if I
have everyone log out and then kill the lockmanager.

The database passes all validity checks and it can properly backup and
restore once the lockmanager has been restarted.

The problem comes back a few weeks later (up to a month).
The database is only 32 GB in size so it is not that large

Is this a known bug? Does anyone know what could cause this?

best regards

Dalton