Hello volkartc,

There is not a workaround for this.

OneFS does not support the use of old linear journal in its system. The journal, which is a part of memory, cannot work well with dual CPU sockets in previous code. Isilon performance heavily depends on the journal. In Gen6.5 nodes running OneFS 9.1 and earlier code, there is only one memory DIMM that is protected by the battery where OneFS stores journal data. This DIMM is controlled by one CPU socket only. If the job thread is running at another socket, every read or write to the journal has to go through the peer CPU socket, causing latency and CPU bandwidth constraints.

@DELL-Sam L​ So there is no way around the check that is done for the upgrade on simulators and users have to completely redo their test systems?  How do the upgrade checks work for physical production Isilon/PowerScale nodes?  I understand that the architecture is different between the physical nodes and the VM simulators, but are they that vastly different?

Hello volkartc,

In a physical the upgrade steps are different and there is a workaround if needed that support can perform to resolve the issue. The simulator is a cut down version, and doesn’t have full capacity as the full version.

Hi @volkartc

I'm facing the exact same issue trying to upgrade my OneFS simulator from 9.4.0.15 to 9.10.1.5 and hitting the following mandatory check failure:

    forbid_old_lj: =====> Checks Failed
    Error: No support for old linear journal in newer OneFS versions

I tried going through an intermediate version (9.7.1.13) hoping it would resolve the journal compatibility issue, but the same check fails at that step too.

Could you let me know how you managed to resolve this?
And if you ended up doing a fresh reinstall, could you share how you backed up and restored your existing configuration of your simulator?

Thanks in advance!