[gpfsug-discuss] logAssertFailed question

[valdis.kletnieks at vt.edu]

On Thu, 09 Aug 2018 15:11:27 -0400, Aaron Knister said:

> We recently had a node running 4.2.3.6 (efix 9billion, sorry can't
> remember the exact efix) go wonky with a logAssertFailed error that
> looked similar to the description of this APAR fixed in 4.2.3.8:
>
> - Fix an assert in BufferDesc::flushBuffer Assert exp(!addrDirty ||
> synchedStale || allDirty inode 554192 block 10 addrDirty 1 synchedStale
> 0 allDirty 0 that can happen during shutdown IJ04520

Yep.  *that* one.  Saw it often enough to put a serious crimp in our style.

'logAssertFailed: ! addrDirty || synchedStale || allDirty'

It's *totally* possible to hit it in the middle of a production workload. I don't
think we ever saw it during shutdown.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180809/21b8d4ca/attachment-0002.sig>