了解如何使用日志排查将数据上传到 Azure Data Box Disk 时出现的问题Understand logs to troubleshoot data upload issues in Azure Data Box Disk

本文适用于 Azure Data Box Disk,描述将数据上传到 Azure 时可能出现的问题。This article applies to Azure Data Box Disk and describes the issues you see when you upload data to Azure.

关于上传日志About upload logs

将数据上传到数据中心内的 Azure 后,系统将为每个存储帐户生成 _error.xml_verbose.xml 文件。When the data is uploaded to Azure at the datacenter, _error.xml and _verbose.xml files are generated for each storage account. 这些日志将上传到用于上传数据的同一个存储帐户。These logs are uploaded to the same storage account that was used to upload data.

这两份日志采用相同的格式,包含将数据从磁盘复制到 Azure 存储帐户时所发生的事件的 XML 描述。Both the logs are in the same format and contain XML descriptions of the events that occurred while copying the data from the disk to the Azure Storage account.

详细日志包含有关每个 Blob 或文件的复制操作状态的完整信息,而错误日志仅包含上传期间遇到错误的 Blob 或文件的信息。The verbose log contains complete information about the status of the copy operation for every blob or file, whereas the error log contains only the information for blobs or files that encountered errors during the upload.

错误日志的结构与详细日志相同,但可在其中筛选出成功的操作。The error log has the same structure as the verbose log, but filters out successful operations.

下载日志Download logs

执行以下步骤找到上传日志。Take the following steps to locate the upload logs.

  1. 如果在将数据上传到 Azure 时出现任何错误,门户会显示诊断日志所在的文件夹的路径。If there are any errors when uploading the data to Azure, the portal displays a path to the folder where the diagnostics logs are located.

    门户中日志的链接

  2. 转到“waies”。Go to waies.

    错误和详细日志

在每种情况下,你都会看到错误日志和详细日志。In each case, you see the error logs and the verbose logs. 选择每个日志并下载本地副本。Select each log and download a local copy.

示例上传日志Sample upload logs

下面显示了 _verbose.xml 的示例。A sample of the _verbose.xml is shown below. 在本例中,订单已成功完成而未出错。In this case, the order has completed successfully with no errors.


<?xml version="1.0" encoding="utf-8"?>
<DriveLog Version="2018-10-01">
  <DriveId>184020D95632</DriveId>
  <Blob Status="Completed">
    <BlobPath>$root/botetapageblob.vhd</BlobPath>
    <FilePath>\PageBlob\botetapageblob.vhd</FilePath>
    <Length>1073742336</Length>
    <ImportDisposition Status="Created">rename</ImportDisposition>
    <PageRangeList>
      <PageRange Offset="0" Length="4194304" Status="Completed" />
      <PageRange Offset="4194304" Length="4194304" Status="Completed" />
      <PageRange Offset="8388608" Length="4194304" Status="Completed" />
      --------CUT-------------------------------------------------------
      <PageRange Offset="1061158912" Length="4194304" Status="Completed" />
      <PageRange Offset="1065353216" Length="4194304" Status="Completed" />
      <PageRange Offset="1069547520" Length="4194304" Status="Completed" />
      <PageRange Offset="1073741824" Length="512" Status="Completed" />
    </PageRangeList>
  </Blob>
  <Blob Status="Completed">
    <BlobPath>$root/botetablockblob.txt</BlobPath>
    <FilePath>\BlockBlob\botetablockblob.txt</FilePath>
    <Length>19</Length>
    <ImportDisposition Status="Created">rename</ImportDisposition>
    <BlockList>
      <Block Offset="0" Length="19" Status="Completed" />
    </BlockList>
  </Blob>
  <File Status="Completed">
    <FileStoragePath>botetaazurefilesfolder/botetaazurefiles.txt</FileStoragePath>
    <FilePath>\AzureFile\botetaazurefilesfolder\botetaazurefiles.txt</FilePath>
    <Length>20</Length>
    <ImportDisposition Status="Created">rename</ImportDisposition>
    <FileRangeList>
      <FileRange Offset="0" Length="20" Status="Completed" />
    </FileRangeList>
  </File>
  <Status>Completed</Status>
</DriveLog>

下面显示了同一订单的 _error.xml 示例。For the same order, a sample of the _error.xml is shown below.


<?xml version="1.0" encoding="utf-8"?>
<DriveLog Version="2018-10-01">
  <DriveId>184020D95632</DriveId>
  <Summary>
    <ValidationErrors>
      <None Count="3" />
    </ValidationErrors>
    <CopyErrors>
      <None Count="3" Description="No errors encountered" />
    </CopyErrors>
  </Summary>
  <Status>Completed</Status>
</DriveLog>

下面显示了 _error.xml 的示例,其中的订单已完成但出错。A sample of the _error.xml is shown below where the order completed with errors.

在本例中,错误文件提供了一个 Summary 节,以及包含所有文件级错误的另一个节。The error file in this case has a Summary section and another section that contains all the file level errors.

Summary 包含 ValidationErrorsCopyErrorsThe Summary contains the ValidationErrors and the CopyErrors. 在本例中,已将 8 个文件或文件夹上传到 Azure,且未出现验证错误。In this case, 8 files or folders were uploaded to Azure and there were no validation errors. 将数据复制到 Azure 存储帐户时,已成功上传 5 个文件或文件夹。When the data was copied to Azure Storage account, 5 files or folders uploaded successfully. 剩余的 3 个文件或文件夹已根据 Azure 容器命名约定重命名,然后成功上传到 Azure。The remaining 3 files or folders were renamed as per the Azure container naming conventions and then uploaded successfully to Azure.

文件级状态位于 BlobStatus 中,描述了上传 Blob 所执行的任何操作。The file level status are in BlobStatus that describes any actions taken to upload the blobs. 在本例中,已重命名 3 个容器,因为数据复制到的文件夹不符合容器的 Azure 命名约定。In this case, three containers are renamed because the folders to which the data was copied did not conform with the Azure naming conventions for containers. 对于在这些容器中上传的 Blob,已包含新的容器名称、Azure 中 Blob 的路径、原始的无效文件路径和 Blob 大小。For the blobs uploaded in those containers, the new container name, path of the blob in Azure, original invalid file path, and the blob size are included.

 <?xml version="1.0" encoding="utf-8"?>
    <DriveLog Version="2018-10-01">
      <DriveId>18041C582D7E</DriveId>
      <Summary>
     <!--Summary for validation and data copy to Azure -->
        <ValidationErrors>
          <None Count="8" />
        </ValidationErrors>
        <CopyErrors>
          <Completed Count="5" Description="No errors encountered" />
          <ContainerRenamed Count="3" Description="Renamed the container as the original container name does not follow Azure conventions." />
        </CopyErrors>
      </Summary>
    <!--List of renamed containers with the new names, new file path in Azure, original invalid file path, and size -->
      <Blob Status="ContainerRenamed">
        <BlobPath>databox-c2073fd1cc379d83e03d6b7acce23a6cf29d1eef/private.vhd</BlobPath>
        <OriginalFilePath>\PageBlob\pageblob test\private.vhd</OriginalFilePath>
        <SizeInBytes>10490880</SizeInBytes>
      </Blob>
      <Blob Status="ContainerRenamed">
        <BlobPath>databox-c2073fd1cc379d83e03d6b7acce23a6cf29d1eef/resource.vhd</BlobPath>
        <OriginalFilePath>\PageBlob\pageblob test\resource.vhd</OriginalFilePath>
        <SizeInBytes>71528448</SizeInBytes>
      </Blob>
      <Blob Status="ContainerRenamed">
        <BlobPath>databox-c2073fd1cc379d83e03d6b7acce23a6cf29d1eef/role.vhd</BlobPath>
        <OriginalFilePath>\PageBlob\pageblob test\role.vhd</OriginalFilePath>
        <SizeInBytes>10490880</SizeInBytes>
      </Blob>
      <Status>CompletedWithErrors</Status>
    </DriveLog>

数据上传错误Data upload errors

下表汇总了将数据上传到 Azure 时生成的错误。The errors generated when uploading the data to Azure are summarized in the following table.

错误代码Error code 说明Description
None 已成功完成。Completed successfully.
Renamed 已成功重命名 Blob。Successfully renamed the blob.
CompletedWithErrors 上传已完成但出错。Upload completed with errors. 错误中的文件的详细信息已包含在日志文件中。The details of the files in error are included in the log file.
Corrupted 数据引入期间计算出的 CRC 与上传期间计算出的 CRC 不匹配。CRC computed during data ingestion doesn't match the CRC computed during upload.
StorageRequestFailed Azure 存储请求失败。Azure storage request failed.
LeasePresent 此项是租用的,已被其他用户使用。This item is leased and is being used by another user.
StorageRequestForbidden 身份验证问题导致无法上传。Could not upload due to authentication issues.
ManagedDiskCreationTerminalFailure 无法作为托管磁盘上传。Could not upload as managed disks. 文件已在临时存储帐户中作为页 Blob 提供。The files are available in the staging storage account as page blobs. 可将页 Blob 手动转换为托管磁盘。You can manually convert page blobs to managed disks.
DiskConversionNotStartedTierInfoMissing 由于 VHD 文件是在预创建的层文件夹外部复制的,因此未创建托管磁盘。Since the VHD file was copied outside of the precreated tier folders, a managed disk wasn't created. 文件已作为页 Blob 上传到创建订单期间指定的临时存储帐户。The file is uploaded as page blob to the staging storage account as specified during order creation. 可手动将其转换为托管磁盘。You can convert it manually to a managed disk.
InvalidWorkitem 无法上传数据,因为它不符合 Azure 命名约定和限制。Could not upload the data as it does not conform to Azure naming and limits conventions.
InvalidPageBlobUploadAsBlockBlob 已作为块 Blob 上传到带有前缀 databoxdisk-invalid-pb- 的容器中。Uploaded as block blobs in a container with prefix databoxdisk-invalid-pb-.
InvalidAzureFileUploadAsBlockBlob 已作为块 Blob 上传到带有前缀 databoxdisk-invalid-af- 的容器中。Uploaded as block blobs in a container with prefix databoxdisk-invalid-af-.
InvalidManagedDiskUploadAsBlockBlob 已作为块 Blob 上传到带有前缀 databoxdisk-invalid-md- 的容器中。Uploaded as block blobs in a container with prefix databoxdisk-invalid-md-.
InvalidManagedDiskUploadAsPageBlob 已作为页 Blob 上传到带有前缀 databoxdisk-invalid-md- 的容器中。Uploaded as page blobs in a container with prefix databoxdisk-invalid-md-.
MovedToOverflowShare 由于原始共享大小超过了最大 Azure 大小限制,已将文件上传到新共享。Uploaded files to a new share as the original share size exceeded the maximum Azure size limit. 新文件共享名称包含带有 -2 后缀的原始名称。The new file share name has the original name suffixed with -2.
MovedToDefaultAzureShare 已将不包含在任何文件夹中的文件上传到默认共享。Uploaded files that weren't a part of any folder to a default share. 共享名称以 databox- 开头。The share name starts with databox-.
ContainerRenamed 这些文件的容器不符合 Azure 命名约定,现已重命名。The container for these files didn't conform to Azure naming conventions and is renamed. 新名称以 databox- 开头,并以原始名称的 SHA1 哈希为后缀The new name starts with databox- and is suffixed with the SHA1 hash of the original name
ShareRenamed 这些文件的共享不符合 Azure 命名约定,现已重命名。The share for these files didn't conform to Azure naming conventions and is renamed. 新名称以 databox- 开头,并以原始名称的 SHA1 哈希为后缀。The new name starts with databox- and is suffixed with the SHA1 hash of the original name.
BlobRenamed 这些文件不符合 Azure 命名约定,已重命名。These files didn't conform to Azure naming conventions and were renamed. 请检查新名称的 BlobPath 字段。Check the BlobPath field for the new name.
FileRenamed 这些文件不符合 Azure 命名约定,已重命名。These files didn't conform to Azure naming conventions and were renamed. 请检查新名称的 FileStoragePath 字段。Check the FileStoragePath field for the new name.
DiskRenamed 这些文件不符合 Azure 命名约定,已重命名。These files didn't conform to Azure naming conventions and were renamed. 请检查新名称的 BlobPath 字段。Check the BlobPath field for the new name.

后续步骤Next steps