keith.smith@mongodb.com said:

Most of the places the block manager code returns EINVAL are via WT_RET_MSG. And we don’t see the corresponding block manager messages in the log; so those aren’t the paths that happened here. The two places where we simply return EINVAL are:

• __wt_block_write_size()  — Are we trying to write a block larger than 4GB.
• __wt_block_addr_invalid()  — Do we have a block address that is past the end of the file

This ticket should update those two places with the right _MSG macros so we know when we return EINVAL from the block manager.