Currently the error-messages generated following an EBUSY return from WiredTiger can be very confronting and opaque.

For example, running a full validate on a WiredTiger collection may sometimes return a transient EBUSY error which is very opaque:

verify() returned EBUSY. Not treating as invalid.

This is actually a warning that something else was accessing a file at the same time (eg. a checkpoint); retrying the validate should succeed.

A more user-friendly error message could clarify the affected file and suggested action, eg:

Could not verify collection-0-1763735954797746426.wt as the file was being actively updated. This should be a transient issue: re-run validate to check again.