Why CloudBlockBlob.StartCopyAsync sometimes writes only 0 bytes?

Question

I have a case that sometimes CloudBlockBlob.StartCopyAsync writes only 0 bytes data into the input asset's blob... What should be the case? So, I decided to start copy while block blob length will not be increased... Any suggestions?

private async Task CreateInputAssetBlobAsync(UploadRequest request)
{
    var cloudBlobContainer = new CloudBlobContainer(request.InputAssetStorageUri);
    var blockBlob = cloudBlobContainer.GetBlockBlobReference(request.BlobName);

    var storageCredentials = new Microsoft.Azure.Storage.Auth.StorageCredentials(_apiAccess.TempBlobAccountName, _apiAccess.TempBlobContainerKey);
    var tempBlobContainer = new CloudBlobContainer(new Uri(_apiAccess.TempBlobContainerAddress), storageCredentials);
    var tempBlockBlob = tempBlobContainer.GetBlockBlobReference(request.BlobName);

    try
    {
        await blockBlob.StartCopyAsync(tempBlockBlob);

        do
        {
            if (blockBlob.CopyState.Status == CopyStatus.Pending)
                await Task.Delay(1000);
            await blockBlob.FetchAttributesAsync();
        }
        while (blockBlob.CopyState.Status != CopyStatus.Success);

        return;
    }
    catch (Exception e)
    {
        Console.WriteLine(e);
        throw;
    }
}

You need to slightly modify your code and write the file copy method as a general function. My code is also copied from the official to modify the test, which should help you. — Jason Pan, Sep 24 '20 at 05:08
If my solution helps you, could you please mark my answer as [accepted](https://meta.stackexchange.com/questions/5234/how-does-accepting-an-answer-work), tks~ — Jason Pan, Sep 28 '20 at 06:22

score 2 · Answer 1 · answered Sep 24 '20 at 04:42

You should use below code when you want to copy the blob content.

For more detail, you can download my sample in github(BlobContainerCopy). It works, and I think it useful to you.

You also can refer to this post. Hope my answer in this post can also help you.

Error during storage blob copy operation - The requested operation is not allowed in the current state of the entity

foreach (ICloudBlob sourceBlobRef in sourceBlobRefs)
{
    if (sourceBlobRef.Properties.ContentType != null)
    {
        // Copy the source blob
        CloudBlockBlob destBlob = destContainer.GetBlockBlobReference(sourceBlobRef.Name);

        try
        {
            //exception throwed here  - StartCopyAsync
            await destBlob.StartCopyAsync(new Uri(GetSharedAccessUri(sourceBlobRef.Name, sourceContainer)));

            ICloudBlob destBlobRef = await destContainer.GetBlobReferenceFromServerAsync(sourceBlobRef.Name);
            while (destBlobRef.CopyState.Status == CopyStatus.Pending)
            {
                Console.WriteLine($"Blob: {destBlobRef.Name}, Copied: {destBlobRef.CopyState.BytesCopied ?? 0} of  {destBlobRef.CopyState.TotalBytes ?? 0}");
                await Task.Delay(500);
                destBlobRef = await destContainer.GetBlobReferenceFromServerAsync(sourceBlobRef.Name);
            }
            Console.WriteLine($"Blob: {destBlob.Name} Complete");
        }
        catch (Exception e)
        {
            Console.WriteLine($"Blob: {destBlob.Name} Copy Failed");
        }
    }
}

Why CloudBlockBlob.StartCopyAsync sometimes writes only 0 bytes?

1 Answers1