| 403 | Instance.IncorrectStatus | The specified instance is in an incorrect status. | 当前状态不允许操作。 | 诊断 |
| 404 | InvalidAccessGroup.NotFound | The specified AccessGroup does not exist. | 您指定的权限组不存在或已删除。 | 诊断 |
| 400 | InvalidAccessGroup.NotsupportedIPv6 | The access group does not support IPv6. | 该权限组不支持IPv6。 | 诊断 |
| 404 | InvalidAccessGroupName.NotAccessRule | There has no rule in access group. | 指定的权限组中无规则。 | 诊断 |
| 404 | InvalidAccessGroupName.NotFound | The specified access group does not exist. | 指定的权限组不存在。 | 诊断 |
| 404 | InvalidAccessRule.NotFound | The specified AccessRule does not exist. | 您指定的权限规则不存在或已删除。 | 诊断 |
| 403 | InvalidAccountStatus.NotEnoughBalance | Your account does not have enough balance. | 您的账户余额不足。 | 诊断 |
| 404 | InvalidAutoRefresh.TooManyAutoRefreshes | The number of auto refreshes exceeds the limit. | 指定的自动更新配置数量超过限制。 | 诊断 |
| 404 | InvalidDataFlow.NotFound | The specified data flow does not exist. | 指定的数据流动不存在。 | 诊断 |
| 404 | InvalidDataType.NotSupported | The data type is not supported. | 指定的数据类型不支持。 | 诊断 |
| 404 | InvalidDescription.InvalidFormat | Description format is invalid. | 指定的描述格式非法。 | 诊断 |
| 403 | InvalidEcsInstanceTypeWithNasProtocolType.NotMatch | The ECS Linux instance can only mount NFS file system. The ECS Windows instance can only mount SMB file system. | 只允许Linux ECS挂载NFS协议的NAS文件系统或者Windows ECS挂载SMB协议的NAS文件系统。 | 诊断 |
| 404 | InvalidEcsInstance.NotFound | The specified EcsInstanceId does not exist. | 指定的ECS实例不存在。 | 诊断 |
| 404 | InvalidExportId.NotFound | The specified ExportId does not exist. | 指定的协议服务导出目录不存在。 | 诊断 |
| 404 | InvalidFileId.NotFound | The specified FileId(%FileId) does not exist. | 指定的文件或目录不存在。 | 诊断 |
| 404 | InvalidFilesetPath.InvalidParameter | Fileset path is invalid. | 指定的Fileset路径无效。 | 诊断 |
| 403 | InvalidFileSystem.AlreadyExisted | The specified file system already exists. | 指定的文件系统已存在。 | 诊断 |
| 404 | InvalidFileSystem.NotFound | The specified file system does not exist. | 指定的文件系统不存在。 | 诊断 |
| 400 | InvalidFileSystem.NotsupportedIPv6 | The file system does not support IPv6. | 该文件系统不支持IPv6。 | 诊断 |
| 404 | InvalidFileSystemPath.InvalidCharacters | The specified fileset path contains invalid characters. | 指定的Fileset路径包含非法字符。 | 诊断 |
| 404 | InvalidFileSystemPath.InvalidCharacters | The specified idir parent path contains invalid characters. | 指定的父目录路径包含非法字符。 | 诊断 |
| 403 | InvalidFileSystemPath.InvalidCharacters | The specified filesystem path contains invalid characters. | 指定的文件系统路径包含非法字符。 | 诊断 |
| 404 | InvalidFileSystemPath.NotDirectory | The specified idir parent path is not directory. | 指定的父目录不是目录。 | 诊断 |
| 404 | InvalidFileSystemPath.NotFound | The specified idir parent path does not exist. | 指定的父目录不存在。 | 诊断 |
| 404 | InvalidFileSystemPath.ParentNotFound | The specified parent path does not exist. | 指定的父目录不存在。 | 诊断 |
| 400 | InvalidFilesystemType.NotSupport | The API operation does not support the file system type. | 当前接口不支持该类型文件系统。 | 诊断 |
| 400 | InvalidFilterName | The specified parameter Filter.1.Name is invalid. | Filter.1.Name值非法。 | 诊断 |
| 404 | InvalidFilterParam | The specified Filter.N.Key is invalid. | 指定的Filter.N.Key参数非法。 | 诊断 |
| 400 | InvalidFilterValue | The specified parameter Filter.1.Value is invalid. | Filter.1.Value值非法。 | 诊断 |
| 404 | InvalidFilterValue | The specified Filter.N.Value is invalid. | 指定的Filter.N.Value参数非法。 | 诊断 |
| 403 | InvalidFset.InUse | Fset already used by other export. | 指定的Fileset已被使用。 | 诊断 |
| 404 | InvalidFsetId.NotFound | The specified Fileset ID does not exist. | 指定的Fileset不存在。 | 诊断 |
| 404 | InvalidJobId.NotFound | The specified JobId(%JobId) does not exist. | 指定的任务ID不存在。 | 诊断 |
| 400 | InvalidLifecyclePolicy.AlreadyExist | The specified LifecyclePolicy already exists. | 指定的生命周期策略已存在。 | 诊断 |
| 400 | InvalidLifecyclePolicy.NotFound | The specified LifecyclePolicy does not exist. | 指定的生命周期策略不存在。 | 诊断 |
| 400 | InvalidLifecycleRetrieveJob.AlreadyExist | The specified LifecycleRetrieveJob already exists. | 指定的数据取回任务已存在。 | 诊断 |
| 404 | InvalidLifecycleRetrieveJob.NotFound | The specified LifecycleRetrieveJob does not exist. | 指定的数据取回任务不存在。 | 诊断 |
| 404 | InvalidLifecycleRule.NotFound | The specified LifecycleRule does not exist. | 指定的生命周期管理规则不存在。 | 诊断 |
| 403 | InvalidMountTarget.AlreadyExisted | The specified mount target already exists. | 指定的挂载点已经存在。 | 诊断 |
| 404 | InvalidMountTarget.NotFound | The specified MountTarget does not exist. | 您指定的挂载点不存在或已删除。 | 诊断 |
| 404 | InvalidMountTarget.NotFound | The specified mount target does not exist. | 指定的挂载点不存在。 | 诊断 |
| 403 | InvalidNetworkType.NotSupported | The specified network type does not supported. | 指定的网络类型不支持。 | 诊断 |
| 400 | InvalidNextToken | The NextToken is invalid. | NextToken参数非法。 | 诊断 |
| 400 | InvalidParam.DualStackMountTargetDomain | The specified dual stack mount target domain does not exist. | 指定的双栈挂载点不存在，请您检查挂载点是否正确。 | 诊断 |
| 400 | InvalidParam.IPAddressIsBlank | The IP address cannot be empty. | 修改的IP不能为空。 | 诊断 |
| 400 | InvalidParam.IPv4AndIPv6MutuallyExclusive | You cannot configure IPv4 and IPv6 at the same time. | IPv4和IPv6不能同时设置。 | 诊断 |
| 400 | InvalidParam.Ipv6SourceCidrIp | IPv6 address verification failed. | IPv6地址校验不通过。 | 诊断 |
| 400 | InvalidParam.MountTargetDomain | The specified mount target domain does not exist. | 指定的挂载点不存在，请您检查挂载点是否正确。 | 诊断 |
| 400 | InvalidParam.NotSupportBYOK | The specified file system type does not support the BYOK encryption function. | 指定文件系统类型不支持用户管理密钥（KMS）加密。 | 诊断 |
| 400 | InvalidParam.SourceCidrIp | IPv4 address verification failed. | IPv4地址校验不通过。 | 诊断 |
| 400 | InvalidParam.TooManyProtocolServiceIds | Too many protocol service ids given. | 一次查询指定的协议服务ID过多。 | 诊断 |
| 400 | InvalidParameter.ProtocolType | Specified parameter ProtocolType is not valid. | 该协议类型不支持。 | 诊断 |
| 400 | InvalidParameter.ConflictVpcCidr | The specified VPC CIDR conflicts with the server. | 指定的VPC网段与服务端冲突。 | 诊断 |
| 404 | InvalidParameter.DirPathNotExist | The Dir Path does not exist | 目录路径不存在 | 诊断 |
| 400 | InvalidParameter.DomainName | DomainName must end with .nas.aliyuncs.com | 挂载地址必须是以 .nas.aliyuncs.com 结尾 | 诊断 |
| 400 | InvalidParameter.EcsLocalPath | EcsLocalPath must start with / | ECS的本地路径必须以 / 开头 | 诊断 |
| 404 | InvalidParameter.InvalidFormat | The EntryList format is invalid. | 指定的EntryList的格式不符合要求。 | 诊断 |
| 400 | InvalidParameter.InvalidKmsKeyId | The specified KMS key ID is invalid. | KMS KeyId为非法值。 | 诊断 |
| 404 | InvalidParameter.InvalidMaxResults | The specified MaxResults is invalid. | 指定的MaxResults非法。 | 诊断 |
| 404 | InvalidParameter.InvalidNextToken | The specified NextToken is invaild. | - | 诊断 |
| 400 | InvalidParameter.KMSKeyId.CMKNotEnabled | The CMK needs to be enabled. | 指定的CMK被disable需要处在启用状态。 | 诊断 |
| 400 | InvalidParameter.KMSKeyId.KMSUnauthorized | KMS is not authorized. | KMS服务未被授权访问。 | 诊断 |
| 400 | InvalidParameter.KmsKeyIdNotFound | The specified KMS key ID does not exist. | KMS KeyId不存在。 | 诊断 |
| 400 | InvalidParameter.KmsServiceNotEnabled | Key Management Service is not enabled. | 未启用KMS服务。 | 诊断 |
| 400 | InvalidParameter.NasRemotePath | NasRemotePath must start with / | NAS挂载路径必须以 / 开头 | 诊断 |
| 404 | InvalidParameter.PathNotExist | The specified path does not exist. | 指定的路径不存在。 | 诊断 |
| 400 | InvalidParameter.PathOrPaths | Either Path or Paths.N must be specified. | Path 和 Paths.N参数必须指定其中一个，并且不能同时指定。 | 诊断 |
| 400 | InvalidParameter.PathsNumberExceed | The maximum number of Path.N for this operation is 10. | 每个策略最多允许关联10个路径。 | 诊断 |
| 404 | InvalidParameter.QuotaNotExistOnPath | The specified path does not exist. | 目录路径不存在，请确认路径。 | 诊断 |
| 403 | InvalidParameter.QuotaPathDepthExceed | The maximum number of Path depth for this operation is 8. | 支持配置配额的最大目录深度为8 | 诊断 |
| 400 | InvalidParameter.ResourceType | The ResourceType is invalid. | ResourceType参数非法 | 诊断 |
| 404 | InvalidParameter.SizeTooLarge | The specified EntryList size exceeds 64 KB. | 指定的EntryList的大小超过64 KB。 | 诊断 |
| 400 | InvalidParameter.TagKey | The specified Tag.n.Key is invalid. | TagKey为非法值。 | 诊断 |
| 400 | InvalidParameter.TagValue | The specified Tag.n.Value is invalid. | TagValue为非法值。 | 诊断 |
| 404 | InvalidParameter.VpcNotFound | The specified VPC does not exist. | 指定的VPC网络不存在。 | 诊断 |
| 404 | InvalidParameter.VpcVswitchMismatch | Given vSwitch mismatch with given VPC. | 指定的VPC和vSwitch不匹配。 | 诊断 |
| 404 | InvalidProtocolService.NotFound | The specified protocol service does not exist. | 指定的协议服务不存在。 | 诊断 |
| 403 | InvalidProtocolSpec.NotSupported | The specified protocol spec does not supported. | 指定的ProtocolSpec不支持。 | 诊断 |
| 403 | InvalidProtocolType.NotSupported | The specified protocol type does not supported. | 指定的协议类型不支持。 | 诊断 |
| 403 | InvalidRamRole.NoPermission | The specified RAM role does not have sufficient permission. | 指定的RAM角色权限不足。 | 诊断 |
| 403 | InvalidRamRole.NotExist | The specified RAM role does not exist. | 指定的RAM角色不存在。 | 诊断 |
| 404 | InvalidRefreshInterval.OutOfBounds | Refresh interval is out of bounds. | 指定的RefreshInterval不在合法范围中。 | 诊断 |
| 404 | InvalidRefreshPath.AlreadyExist | The refresh path already exists. | 指定的自动更新目录已存在。 | 诊断 |
| 404 | InvalidRefreshPath.Duplicated | Refresh path is duplicated. | 指定的自动更新目录的路径重复。 | 诊断 |
| 404 | InvalidRefreshPath.InvalidParameter | Refresh path is invalid. | 指定的自动更新目录的路径非法。 | 诊断 |
| 404 | InvalidRefreshPath.NotFound | Refresh path does not exist. | 指定的自动更新目录不存在。 | 诊断 |
| 404 | InvalidRefreshPath.TooManyPaths | The number of refresh paths exceeds the limit. | 查询的自动更新目录数量超过限制。 | 诊断 |
| 404 | InvalidRefreshPolicy.InvalidParameter | Refresh policy is invalid. | 自动更新策略非法。 | 诊断 |
| 400 | InvalidResourceId.NotFound | The ResourceId does not exist. | ResourceId不存在。 | 诊断 |
| 404 | InvalidSourceSecurityType.NotSupport | The source security type is not supported. | 指定的源端存储的安全保护类型不支持。 | 诊断 |
| 404 | InvalidSourceStorage.InvalidParameter | Source storage has invalid parameters. | 指定的源端存储路径非法。 | 诊断 |
| 404 | InvalidSourceStorage.InvalidRegion | Source storage region is invalid. | 源端存储的区域异常，请检查源端存与CPFS是否在同一个region。 | 诊断 |
| 404 | InvalidSourceStorage.NeedVersioning | Source storage must enable versioning. | 源端存储需要打开多版本功能。 | 诊断 |
| 404 | InvalidSourceStorage.NotFound | Source storage is not found. | 指定的源端存储不存在。 | 诊断 |
| 404 | InvalidSourceStorage.NotSupport | Source storage type is not supported. | 指定的源端存储的类型不支持。 | 诊断 |
| 404 | InvalidSourceStorage.PermissionDenied | The source storage access permission is denied. | 无源端存储访问权限，请检查SLR授权、源存储的访问tag。 | 诊断 |
| 404 | InvalidSourceStorage.Unreachable | Source storage cannot be accessed. | 源端存储无法访问。 | 诊断 |
| 404 | InvalidSrcTaskId.NotFound | The SrcTaskId is not found. | 指定的 SrcTaskId 不存在。 | 诊断 |
| 404 | InvalidSrcTaskId.TaskIdInvalid | Source task ID is invalid. | 指定的需要复制的任务 ID 非法 | 诊断 |
| 404 | InvalidSrcTaskId.TaskIdNotFound | Source task ID is not found. | 指定的需要复制的任务 ID 不存在。 | 诊断 |
| 400 | InvalidStatus | Specified parameter Status is not valid. | 指定的Status非法。 | 诊断 |
| 403 | InvalidStatus.NotSupported | The specified protocol service status does not support. | 指定的协议机集群状态不支持。 | 诊断 |
| 403 | InvalidTargetFileId.NotDirectory | The specified TargetFileId(%
TargetFileId) is not directory. | 指定的目标不是目录。 | 诊断 |
| 404 | InvalidTargetFileId.NotFound | The specified TargetFileId(%TargetFileId) does not exist. | 指定的目标目录不存在。 | 诊断 |
| 404 | InvalidTaskAction.NotSupported | The task action is not supported. | 指定的任务类型不支持。 | 诊断 |
| 404 | InvalidTaskAction.PermissionDenied | The task action is not allowed. | 指定的任务类型不允许，例如复制系统。 | 诊断 |
| 404 | InvalidTaskId.NotFound | The specified task ID does not exist. | 指定的数据流动TaskId不存在。 | 诊断 |
| 404 | InvalidThroughput.OutOfBounds | Throughput is out of bounds. | 指定的Throughput不在合法范围中。 | 诊断 |
| 400 | InvalidVolumeId.NotSupportedFileSystemType | The specified file system ID is invalid. | 文件系统类型不支持 | 诊断 |
| 404 | InvalidVpcId.ConflictVpcCidr | Vpc cidr conflict with file system | 指定VPC与文件系统VPC网段重叠。 | 诊断 |
| 403 | InvalidVpcId.CrossVpcNotSupport. | Cross VPC not support. | 不支持协议服务和文件系统跨VPC。 | 诊断 |
| 403 | InvalidVSwitchId.IpShortage | The specified vswitch ip shortage. | 指定的vSwitch可用IP不足。 | 诊断 |
| 400 | MissingAccessGroupName | AccessGroupName is mandatory for this action. | 未指定权限组。 | 诊断 |
| 400 | MissingDataFlowId | DataFlowId is mandatory for this action. | 未指定DataFlowId参数。 | 诊断 |
| 400 | MissingDataType | DataType is mandatory for this action. | 指定的DataType参数。 | 诊断 |
| 400 | MissingEntryList | EntryList is mandatory for this action. | 指定的EntryList参数。 | 诊断 |
| 400 | MissingExportId | ExportId is mandatory for this action. | 未指定ExportId参数。 | 诊断 |
| 400 | MissingFileId | FileId is mandatory for this action. | 缺少FileId参数。 | 诊断 |
| 400 | MissingFileSystemId | FileSystemId is mandatory for this action. | 未指定FileSystemId参数。 | 诊断 |
| 400 | MissingFileSystemPath | FileSystemPath is mandatory for this action. | 缺少FileSystemPath参数。 | 诊断 |
| 400 | MissingFsetId | FsetId is mandatory for this action. | 未指定Fileset ID参数。 | 诊断 |
| 400 | MissingIdirId | IdirId is mandatory for this action. | 缺少 IdirId 参数。 | 诊断 |
| 400 | MissingJobId | JobId is mandatory for this action. | 缺少JobId参数。 | 诊断 |
| 400 | MissingParameter.AccessGroupName | You must specify AccessGroupName when you create a standard or extreme file system mount target. | 创建通用型或极速型文件系统挂载点时权限组参数必填。 | 诊断 |
| 400 | MissingParameter.KmsKeyId | When parameter EncryptType equals 2, the parameter KmsKeyId is mandatory for your request. | 当加密类型为用户管理密钥（KMS）时，KmsKeyId参数必填。 | 诊断 |
| 400 | MissingParameter.ResourceIdOrTag | Either ResourceId or Tag must be specified. | ResourceId和Tag至少有一个必填。 | 诊断 |
| 400 | MissingParameter.ResourceIds | You must specify ResourceIds. | ResourceId不能为空。 | 诊断 |
| 400 | MissingParentPath | IdirParentPath is mandatory for this action. | 缺少IdirParentPath参数。 | 诊断 |
| 400 | MissingProtocolServiceId | ProtocolServiceId is mandatory for this action. | 未指定ProtocolServiceId参数。 | 诊断 |
| 400 | MissingSourceStorage | SourceStorage is mandatory for this action. | 未指定SourceStorage参数。 | 诊断 |
| 400 | MissingSrcTaskId | SrcTaskId is mandatory for this action. | 指定的SrcTaskId参数。 | 诊断 |
| 400 | MissingTargetFileId | TargetFileId is mandatory for this action. | 缺少TargetFileId参数。 | 诊断 |
| 400 | MissingTaskId | TaskId is mandatory for this action. | 未指定TaskId参数。 | 诊断 |
| 400 | MissingThroughput | Throughput is mandatory for this action. | 未指定Throughput参数。 | 诊断 |
| 400 | MissingVpcId | VpcId is mandatory for this action. | 未指定VPC ID参数。 | 诊断 |
| 403 | MntPathConflict.InvalidParam | FilesetId and Path must and can only be specified one. | Fileset和Path只能且必须指定一个。 | 诊断 |
| 403 | NoPermission.SystemTag | You are not authorized to operate the system tag. The product code is invalid. | 没有权限操作此系统标签，服务账户code值非法。 | 诊断 |
| 400 | NumberExceed.ResourceIds | The maximum number of ResourceIds is exceeded. The maximum is 50. | 传入的资源ID数量达到上限，最多支持50个。 | 诊断 |
| 400 | NumberExceed.Tags | The maximum number of Tags is exceeded. The maximum is 20. | 传入的Tag数量达到上限，最多支持20个。 | 诊断 |
| 403 | OperationDenied.AlreadyExists | The operation is denied due to IdirName already exists in parent path. | 创建的目录名在父目录中已存在。 | 诊断 |
| 403 | OperationDenied.AutoRefreshNotSupport | The operation is denied. Auto refresh is not supported. | 该文件系统不支持自动更新。 | 诊断 |
| 403 | OperationDenied.Conflict | The operation is in conflict with (% JobId). Please try again later. | 请求与其他job有冲突，请稍后再试。 | 诊断 |
| 403 | OperationDenied.ConflictOperation | The operation is denied due to a conflict with an ongoing operation. | 与当前的文件系统操作冲突导致无法创建数据流动。 | 诊断 |
| 403 | OperationDenied.CrossVPCExccedLimit | Cross vpc mount exceed limit. | 跨VPC挂载点个数超出限制。 | 诊断 |
| 403 | OperationDenied.CrossVPCExceedLimit | Cross vpc mount exceed limit. | 跨VPC导出目录数量超过当前协议服务规格上限。 | 诊断 |
| 403 | OperationDenied.DataFlowNotSupported | The operation is not supported. | 该文件系统不支持数据流动。 | 诊断 |
| 403 | OperationDenied.DependBucketTag | The operation is denied. The OSS Bucket tag cpfs-dataflow is missing. | 由于OSS Bucket未打上cpfs-dataflow标签，创建数据流动失败。 | 诊断 |
| 403 | OperationDenied.DependencyViolation | The operation is denied due to dependancy violation. | 进行该操作的条件不满足。 | 诊断 |
| 403 | OperationDenied.DependFset | The operation is denied due to invalid fileset state. | 由于fileset状态异常创建数据流动失败。 | 诊断 |
| 403 | OperationDenied.DependMountpoint | The operation is denied because no mount point is found. | 由于文件系统没有挂载点导致创建数据流动失败。 | 诊断 |
| 403 | OperationDenied.DirQuotaAssociated | The specified FileSystem has DirQuota associated. | 当前文件系统目录设置了配额管理，删除文件系统前请先删除配额管理。 | 诊断 |
| 400 | OperationDenied.EncryptedFileSystemNotSupportedForLifecycle | The encrypted file system does not support lifecycle. | 加密的文件系统不支持生命周期管理。 | 诊断 |
| 403 | OperationDenied.FilesetNotSupported | The operation is not supported. | 该文件系统不支持Fileset。 | 诊断 |
| 400 | OperationDenied.FileSystemNotSupportedForLifecycle | The file system does not support lifecycle. | 指定的文件系统不支持生命周期管理。 | 诊断 |
| 403 | OperationDenied.FsetAlreadyInUse | The Fset is already bound to another data flow. | Fset已经被使用。 | 诊断 |
| 403 | OperationDenied.InvalidMntStatus | The operation is denied due to invalid protocol mount targte status. | - | 诊断 |
| 400 | OperationDenied.InvalidNextToken | The specified NextToken is invalid. | 指定的NextToken参数非法。 | 诊断 |
| 403 | OperationDenied.InvalidPtcStatus | The operation is denied due to invalid protocol service status. | 当前协议服务状态不支持该操作。 | 诊断 |
| 403 | OperationDenied.InvalidState | The operation is denied due to invalid file system state. | 当前文件系统状态不支持该操作。 | 诊断 |
| 403 | OperationDenied.InvalidState | The operation is not permitted when the status is processing. | 状态处理中不允许此操作。 | 诊断 |
| 403 | OperationDenied.KeyDoubleScope | The same key can only have one scope. | 同一个系统标签key,只能设置相同的scope类型，此操作将导致同一个系统标签key拥有不同的scope类型。 | 诊断 |
| 403 | OperationDenied.KeyValueNotNull | The key value cannot be null. | 标签值不能为空。 | 诊断 |
| 400 | OperationDenied.LifecyclePolicyAssociated | The specified FileSystem has LifecyclePolicy associated. | 当前文件系统已关联生命周期策略，删除文件系统前请先删除关联的生命周期策略。 | 诊断 |
| 400 | OperationDenied.LifecyclePolicyCountLimitExceeded | The maximum number of LifecyclePolicies is exceeded. | 生命周期策略数量达到上限。 | 诊断 |
| 400 | OperationDenied.LifecycleRecycleBinTieringJobAssociated | The specified FileSystem has LifecycleRecycleBinTieringJob associated. | 回收站后台任务占用。 | 诊断 |
| 400 | OperationDenied.LifecycleRetrieveJobCountLimitExceeded | The maximum number of LifecycleRetrieveJobs is exceeded. | 数据取回任务数量达到上限。 | 诊断 |
| 400 | OperationDenied.LifecycleRetrieveJobEnded | The specified LifecycleRetrieveJob has already ended. | 指定的数据取回任务已经执行完毕。 | 诊断 |
| 400 | OperationDenied.LifecycleRetrieveJobNotFailed | The specified LifecycleRetrieveJob has not failed. | 指定的数据取回任务未失败。 | 诊断 |
| 403 | OperationDenied.MountTargetExceedLimit | The maximum number of mount target in the specified file system is exceeded. | 当前文件系统的挂载点达到上限。 | 诊断 |
| 403 | OperationDenied.NestedDir | The operation is denied due to nested directory. | 目录存在嵌套导致无法创建自动更新配置。 | 诊断 |
| 403 | OperationDenied.NoMountTargetQuota | No mount target quota on this protocol service. | 协议服务的导出目录配额耗尽。 | 诊断 |
| 403 | OperationDenied.NoProtocolServiceQuota | No protocol service quota. | 当前文件系统协议服务配额用尽。 | 诊断 |
| 404 | OperationDenied.NoStock | The operation is denied due to no stock. | 文件系统无库存。 | 诊断 |
| 403 | OperationDenied.NotServiceAccount | Only service account is authorized to perform the operation. | 只有服务账户允许此操作。 | 诊断 |
| 403 | OperationDenied.NotSupported | The operation is denied due to not supported. | 文件系统不支持协议机服务。 | 诊断 |
| 403 | OperationDenied.NotSupportPaths.N | Your request does not meet the gray condition. The Paths.N parameter is not supported. | 当前请求未通过灰度策略，不持支Paths.N参数。 | 诊断 |
| 403 | OperationDenied.NotSupport | The operation is not supported. | 不允许此操作。 | 诊断 |
| 403 | OperationDenied.ProtocolServiceExceedLimit | The protocol service amount exceed file system limit. | 协议服务数量超过文件系统限制。 | 诊断 |
| 403 | OperationDenied.RecycleBinDisabled | The operation is denied because the recycle bin is disabled. | 请求无法在回收站关闭状态下执行。 | 诊断 |
| 403 | OperationDenied.RecycleBinEnabled | The recycle bin is already enabled. | 回收站已经处于开启状态。 | 诊断 |
| 403 | OperationDenied.TooManyDepths | The operation is denied due to Fileset path too deep. | Fileset目录路径深度超过阈值。 | 诊断 |
| 403 | OperationDenied.TooManyFilesets | The operation is denied due to too many fileset in filesystem. | 文件系统的Fileset目录数量超过阈值。 | 诊断 |
| 403 | OperationDenied.TooManyIdirs | The operation is denied due to too many Idirs in filesystem. | 文件系统的智能目录数量超过阈值。 | 诊断 |
| 403 | OperationDenied.TooManyRunningJobs | The maximum number of running job is one. Please try again later. | 运行中的job不能超过1个，请稍后再试。 | 诊断 |
| 400 | ORDER.OPEND | You have already purchased the NAS service. Go to the NAS console to start using it. | 您已开通NAS服务，请前往控制台使用。 | 诊断 |
| 404 | PathNotExistInFileSystem.InvalidParam | Given path does not exist in file system. | 文件系统中不存在指定的路径。 | 诊断 |
| 403 | PermissionDenied.CapacityTooLow | Capacity of file system too low to subscribe protocol service. | 容量低于10800GiB不允许开通协议服务。 | 诊断 |
| 403 | PermissionDenied.CLThroughputInvalid | Throughput of caching protocol service is invalid. | 缓存型协议服务带宽无效。 | 诊断 |
| 403 | PermissionDenied.ThroughputExceed | Throughput of protocol service must less than throughput of file system. | 协议服务的带宽不允许超过文件系统的带宽。 | 诊断 |
| 403 | PermissionDenied.ThroughputInvalid | Standard protocol service should not specified throughput. | 通用型协议服务不允许指定服务带宽。 | 诊断 |
| 403 | PermissionDenied.ThroughputTooSmall | Throughput of protocol service too small. | 协议服务带宽太小，不满足开通条件。 | 诊断 |
| 400 | Region.NotSupported | The specified Region is not supported for this API now. | 当前地域暂不支持该功能。 | 诊断 |
| 400 | RepeatListParameter.TooManyRepeatListItems | You can only specify one repeat list item for the parameter Filter. | Filter只能传入一个过滤字段。 | 诊断 |
| 202 | RequestAccepted | The request has been accepted by the server. | 请求已被后端接受。 | 诊断 |
| 403 | Resource.OutOfStock | The inventory of the specified zone is insufficient. | 指定的可用区库存不足。 | 诊断 |
| 400 | ResultOutputTooLong | The maximum length of the mount info result output is exceeded. | 挂载详情信息过长 | 诊断 |
| 400 | SubAccount.NoEncryptionSLRPermission | The RAM user does not have the permission to create service linked role AliyunServiceRoleForNasEncryption. Please authorize the RAM user the permission ram:CreateServiceLinkedRole. | 当前RAM用户没有权限创建AliyunServiceRoleForNasEncryption SLR角色，请授权RAM用户ram:CreateServiceLinkedRole权限。 | 诊断 |
| 400 | SubAccount.NoExtremeSLRPermission | The RAM user does not have the permission to create service linked role AliyunServiceRoleForNasExtreme. Please authorize the RAM user the permission ram:CreateServiceLinkedRole. | 当前RAM用户没有权限创建AliyunServiceRoleForNasExtreme SLR角色，请授权RAM用户ram:CreateServiceLinkedRole权限。 | 诊断 |
| 400 | SubAccount.NoLogSLRPermission | The RAM user does not have the permission to create service linked role AliyunServiceRoleForNasLogDelivery. Please authorize the RAM user the permission ram:CreateServiceLinkedRole. | 当前RAM用户没有权限创建AliyunServiceRoleForNasLogDelivery SLR角色，请授权RAM用户ram:CreateServiceLinkedRole权限。 | 诊断 |
| 400 | SubAccount.NoNasEcsHandlerSLRPermission | The RAM account cannot create the AliyunServiceRoleForNasEcsHandler service linked role. The ram:CreateServiceLinkedRole permission is required. | 子账户无法创建AliyunServiceRoleForNasEcsHandler SLR 角色，需要ram:CreateServiceLinkedRole权限 | 诊断 |
| 400 | SubAccount.NoSLRPermission | The RAM account cannot create the service linked role. The ram:CreateServiceLinkedRole permission is required. | 子账号无法创建 SLR 角色，需要ram:CreateServiceLinkedRole权限 | 诊断 |
| 400 | SubAccount.NoStandardSLRPermission | The RAM user does not have the permission to create service linked role AliyunServiceRoleForNasStandard. Please authorize the RAM user the permission ram:CreateServiceLinkedRole. | 当前RAM用户没有权限创建AliyunServiceRoleForNasStandard SLR角色，请授权RAM用户ram:CreateServiceLinkedRole权限。 | 诊断 |
| 400 | SystemTag.NumberExceed | The maximum number of system tags for each resource is 50. | 每个资源最多允许绑定50个系统标签。 | 诊断 |
| 403 | UserDisabled | NAS has not been activated for your account, or your account does not have sufficient balance. | 您的账户尚未开通 Nas 服务或余额不足。 | 诊断 |
| 404 | InvalidParameter.VswNotFound | The specified vSwitch does not exist. | 指定的虚拟交换机不存在。 | 诊断 |
| 400 | MissingVSwitchId | vSwitchId is mandatory for this action. | 未指定vSwitch ID参数。 | 诊断 |
| 400 | InvalidVSwitch.Ipv6NotTurnOn | The vSwitch you are currently using has not enabled the IPv6 function. Please enable this function first and try again. | 您当前使用的交换机不支持IPv6功能，请开启此功能后重试。 | 诊断 |
| 400 | InvalidVSwitchId.IpNotEnough | The number of the specified vSwitch IP address is insufficient. | 指定的交换机IP数量不足。 | 诊断 |