luminous: write following remove might access previous onode
So the sequence is as follows:
In Luminous there is a chance that A is removed from the cache (as no ref is taken) before T1 lands to DB.
Subsequent B might access outdated onode A from DB and proceed with invalid A state.
Which finally results in, e.g. duplicate removal from the allocator.
Final symptoms remind #38049 and #36541 but the root cause is different.
This has been fixed in Mimic+ by