Hi Helen,

>>> On Linux, if you brought this database forward from an earlier version, try switching FW off, restart server, then switch it on again and restart server.
>>>
>>>
>> I missed this point. Upgrading from 2.0 to 2.1.1 backup and restore of
>> database isn't enough?
>> Migration and installation doc doesn't say anything about forced writes.
>>
>
> Actually, in the release notes, quite some prominence is given to the discovery (late in the 2.1 beta phase) that FW never worked on Linux. A workaround was done and backported to v.2.0.4.

I know well this, but the point is about switching off and then on fw
after upgrading a Linux server (say from 2.0 to 2.1.1).
From your sentence seems that upgrading the server isn't enough, like
database has a memory of incorrect management of forced writes. AFAIR in
Linux a particular option in ioctl() isn't supported, so forced writes
has changed in "close and reopen" file descriptor.
I don't understand why to switch off and then on the database's forced
writes.

Ciao.
Mimmo.