Lock-free reads must be able to handle AutoGetCollectionForReadLockFree being instantiated under an AutoGetCollectionForRead that has already opened a storage snapshot/transaction. OR, abandonSnapshot() must be called before or in AutoGetCollectionForReadLockFree somehow.

Scenario where the bug surfaced:
dumpChunks uses a DBDirectClient for a query. There is an AutoGetCollectionForRead instantiated already instantiated. A query was in-progress when the error occurred that resulted in the DBDirectClient use for better error reporting.