Under certain circumstances it is possible that fetching cache files from DFS will fail.
While this is an expected situation (caused by network/NFS issues, for example), the generated error message is some cases is incoherent:
The problem is that the local file size is checked against the dfs file size, and the error message displays the local file size and metadata size.
This has occurred in live environment and appears to be impractical to reproduce on a test env.
It is possible/likely that either the dfs file size or metadata changes while the _fetch() method is being executed.
Suggested course of action would be to either fix the error message, or
reload the dfs filesize / metadata size if both mismatch.