Hi!

We had similar problems.

Our storages have 8GB RAM and the errors occured on the 2nd 4,5GB file.
So it looks as if the storage was cahing into memory and when the cache was full the error occured.

Are you using replication / snapshots?

We are replicating one storage to another one and on the destination we made snapshots of the destination volume.

We deleted the snapshot, stopped the replication and started both again.

Then everything was fine again.

DerFux