Highlighted
HZD_Mai
1 Nickel

Blob could not be stored on write or could not be found on import

Hello guys,

we have a small problem with our communication to the Centera. We are using most recent EMC SDK (Version) and .NetWrapper. Since a few weeks we get sporadic the following error message while retrieving files out of Centera:

Blob could not be stored on write or could not be found on import (transid=Servername/141770/READ_BLOB') ---> error: -10014, error text: FP_FILE_NOT_STORED_ERR, syserror: 2, message: Blob could not be stored on write or could not be found on import (transid=Servername/141770/READ_BLOB'), trace: NetworkPacket.checkControl(2)<HPPReadBlobTransaction.readBytes(HPPImportData&)<HPPReadBlobTransaction.run()<ClusterCloud::readBlob(FPBasicGenericStream*,42EHCL7SFFKFUe85F4DVT302E64,20R4GPQDIBVMOx56VTL7OSLCEN6G54PSNRN8IH809VO512D3697OI,0,1604538,1604538,0)<FPTag.blobRead<FPTag_BlobRead(-,-,0)

Retrying the operation succeeds and thus proves that the file is properly stored.

Checking the network errors showed no results.

Any hint for a reason will be appreciated.

Thanks and best regards

Dirk Maifarth

0 Kudos
1 Reply
gstuartemc
2 Iron

Re: Blob could not be stored on write or could not be found on import

Hi Dirk - this is not an SDK issue, the SDK is simply reporting back that the cluster was unable to properly store the blob. This can happen for a variety of reasons (Access or Storage Node problems, cluster being swamped with requests, network issues etc) and the correct procedure is to trap the error and retry the write operation. As you appear to be doing that already then your application is handling things correctly.

If you continue to see these issues on a reular basis I suggest you log a support call with EMC Global Support and they can work with you by investigating the cluster logs for the transactions that gave this error (e.g. Servername/141770).

0 Kudos