错误码
|
HTTP status code |
错误码 |
错误信息 |
描述 |
操作 |
| 403 | AccessGroup.HasAccessRule | The current access group cannot be deleted because it contains rules. | 当前权限组下存在权限组规则，无法删除。 | 诊断 |
| 403 | AccessGroup.NameExist | An access group instance with the same name already exists. | 已存在同名权限组实例，请您选用其他名字。 | 诊断 |
| 403 | AccessGroup.ReferenceByMountPoint | The current access group cannot be deleted because it is referenced by mount points. | 当前权限组被挂载点引用，无法删除。 | 诊断 |
| 403 | AccessGroup.TooMany | The maximum number of access groups is exceeded. | 权限组数量已经超过限制，无法继续创建。 | 诊断 |
| 403 | AccessRule.NetworkSegmentExist | An error occurred. An access group rule already exists for the specified network segment. You can modify the existing rule to implement access control. | 已经存在一条关于该网络地址(段)的权限组规则，无法继续创建。可以通过修改已有权限组规则来实现访问控制。 | 诊断 |
| 403 | AccessRule.TooMany | The maximum number of access groups is exceeded. | 权限组数量已经超过限制，无法继续创建。 | 诊断 |
| 400 | DirectoryQosLimit.DirectoryQosLimitNotExists | DirectoryQosLimit not exists. | 目录流控规则不存在 | 诊断 |
| 400 | DirectoryQosLimit.FileSystemNotExists | FileSystem not exists. | 文件系统不存在 | 诊断 |
| 400 | DirectoryQosLimit.InvalidParam | %s. | 输入参数不合法 | 诊断 |
| 400 | DirectoryQosLimit.TooMany | %s. | 创建的目录流控规则数量已到达上限 | 诊断 |
| 400 | Federation.InvalidParam | %s. | Federation参数非法 | 诊断 |
| 400 | FileSystem.FunctionTooFrequently | Function too frequently, please try again. | 多次方法调用时间间隔过小，请重试。 | 诊断 |
| 403 | FileSystem.HasMountPoint | The current file system instance cannot be deleted because it contains mount points. | 当前文件系统实例下存在挂载点，无法删除。 | 诊断 |
| 403 | FileSystem.TooMany | The maximum number of file system instances is exceeded. | 文件系统实例数量已经超过限制，无法继续创建。 | 诊断 |
| 400 | IdempotentParameterMismatch | The request uses the same client token as a previous, but non-identical request. Do not reuse a client token with different requests, unless the requests are identical. | 用于幂等的 client token 数值不一致。 | 诊断 |
| 500 | InternalError | An internal error occurred. Please try again. If the error persists, submit a ticket. | 内部错误。建议重试，如果多次重试报错请提交工单。 | 诊断 |
| 400 | InvalidParameter.AccessGroupNotFound | No access group instance is found. The instance may have been deleted or an incorrect access group ID was used. | 未发现权限组实例。实例可能已经被删除，或者使用了错误的权限组ID。 | 诊断 |
| 400 | InvalidParameter.AccessRuleNotFound | The specified access rule is not found. The rule may have been deleted, or the rule ID is incorrect. | 未发现权限组规则。权限组规则可能已经被删除，或者使用了错误的权限组规则ID。 | 诊断 |
| 400 | InvalidParameter.FileSystemInvalidCapacity | The specified file system capacity is invalid. For more information, see API reference and DFS restrictions. | 非法的文件系统空间参数，请查阅API文档说明和DFS使用限制。 | 诊断 |
| 400 | InvalidParameter.FileSystemNameExist | File system instance with the same name already exist. | 已存在同名文件系统实例，请您选用其他名字。 | 诊断 |
| 400 | InvalidParameter.FileSystemNotFound | The specified file system instance is not found. The instance may have been deleted, or the instance ID is incorrect. | 未发现文件系统实例。文件系统实例可能已经被删除，或者使用了错误的文件系统实例ID。 | 诊断 |
| 400 | InvalidParameter.InvalidNetworkFormat | The specified network segment for the access rule is incorrectly formatted. For more information, see API reference. | 创建权限组规则时，传入的授权地址格式错误，请查阅API说明文档。 | 诊断 |
| 400 | InvalidParameter.InvalidParameter | The specified parameters are invalid. Follow the instructions in API reference to make a modification. | 非法参数，请参照API说明文档进行核对修正。 | 诊断 |
| 400 | InvalidParameter.MissingRequiredParameter | Required parameters are missing. Follow the instructions in the API reference to make a modification and try again. | 必填参数没有填。请查阅API文档修正，并重试。 | 诊断 |
| 400 | InvalidParameter.MountPointInvalidStatus | The specified mount point status is invalid. For more information, see API reference. | 非法的挂载点状态，请查阅API文档。 | 诊断 |
| 400 | InvalidParameter.MountPointInvalidVpc | The VPC ID used to create the mount point is invalid. Possible causes include: The used VPC ID is incorrect, the VPC and the file system are in different regions, or the VSwitch ID of the VPC does not belong to the VPC. | 创建挂载点时使用了错误的VPC网络ID。可能使用了错误的VPC网络ID，或者VPC网络与文件系统不在同一地域，或者VPC虚拟交换机ID不属于VPC网络。 | 诊断 |
| 400 | InvalidParameter.MountPointInvalidVswitch | The VSwitch ID used to create the mount point is invalid. Possible causes include: The used VSwitch ID is incorrect, or the VSwitch and the file system are in different regions. | 创建挂载点时使用了错误的VPC网络交换机ID。可能使用了错误的VPC网络交换机ID，或者VPC网络交换机与文件系统不在同一地域。 | 诊断 |
| 400 | InvalidParameter.MountPointNotFound | No mount point instance is found. The instance may have been deleted, or an incorrect mount point ID was used. | 未发现挂载点实例。实例可能已经被删除，或者使用了错误的挂载点ID。 | 诊断 |
| 400 | InvalidParameter.RegionNotMatch | The specified region in the request does not match the region in the backend service. | 请求携带的Region信息与后端服务所在的Region不匹配。 | 诊断 |
| 400 | InvalidParameter.UnsupportedApi | DFS does not support the specified API. | DFS不支持该API | 诊断 |
| 400 | InvalidParameter.UnsupportedCallerType | DFS does not support the specified account type. | DFS尚未支持该账号类型。 | 诊断 |
| 400 | InvalidParameter.UnsupportedContentType | The content-type parameter in the HTTP request is not supported. Submit a ticket. | 不支持HTTP请求中携带的content-type，请提交工单。 | 诊断 |
| 400 | InvalidParameter.UserGroupsMappingInvalidGroupName | Invalid group name | 组名不合法。 | 诊断 |
| 400 | InvalidParameter.UserGroupsMappingInvalidUserName | Invalid user name | 用户名不合法。 | 诊断 |
| 400 | InvalidParameter.VscAgentNotExist | VscAgentId Not Exist | vsc agent id不存在 | 诊断 |
| 403 | MountPoint.Exist | A mount point has already been created for the specified VSwitch and access group. Use different VSwitch or access group to create the mount point. | 同一个VPC虚拟交换机和权限组组合下只能创建一个挂载点。请使用其他VPC虚拟交换机或权限组创建挂载点。 | 诊断 |
| 403 | MountPoint.TooMany | The maximum number of the mount points in the specified file system is exceeded. | 该文件系统下的挂载点数量已经超过限制，无法继续创建。 | 诊断 |
| 404 | PosixFileSystem.NotFound | Posix file system not found. | 找不到Posix文件系统 | 诊断 |
| 400 | PosixFileSystem.NotSupport | Posix interface not support now. | Posix功能当前未开放。 | 诊断 |
| 403 | QosPolicy.DefinitionConflict | %s. | QosPolicy定义冲突 | 诊断 |
| 403 | QosPolicy.FederationNotExists | %s. | Federation不存在 | 诊断 |
| 403 | QosPolicy.FileSystemNotExists | Filesystem not found. | 文件系统不存在 | 诊断 |
| 403 | QosPolicy.FlowIdInvalid | %s. | FlowId非法 | 诊断 |
| 403 | QosPolicy.InvalidParam | %s. | QosPolicy参数非法 | 诊断 |
| 403 | QosPolicy.QosPolicyNotExists | %s. | QosPolicy不存在 | 诊断 |
| 403 | QosPolicy.QosPolicyTooMany | QosPolicy Count Limit Exceeded. | 用户创建的QosPolicy数量达到了上限 | 诊断 |
| 403 | QosPolicy.ZoneIdInvalid | %s. | ZoneId非法 | 诊断 |
| 403 | Ram.DfsCheckFailed | You have failed RAM authorization check. Check whether the account has sufficient permissions. | 未通过权限检查，请检查账号是否有足够的权限。 | 诊断 |
| 403 | Ram.VpcCheckFailed | You have failed RAM authorization check. Check whether you have sufficient permissions to operate on the resources of the specified VPC. | 未通过权限检查，请检查是否有足够权限操作该VPC资源。 | 诊断 |
| 503 | ServiceBusy | The service is unavailable now. Please try again later. | 服务忙，请稍后重试。 | 诊断 |
| 503 | ServiceUnavailable | The service is unavailable now. The system is being updated. Please try again later. | 服务暂时不可用（底层服务不可用）。系统正在升级，暂时不可用，可稍后尝试。 | 诊断 |
| 403 | Sts.DfsCheckFailed | You have failed STS authorization check. Check whether you have sufficient permissions. | 未通过STS权限检查，请检查是否有足够权限。 | 诊断 |
| 403 | Sts.VpcCheckFailed | You have failed STS authorization check. Check whether you have sufficient permissions to operate on the resources of the specified VPC. | 未通过STS权限检查，请检查是否有足够权限操作该VPC资源。 | 诊断 |
| 403 | User.Disabled | You have not activated DFS. | 您尚未开通DFS服务。 | 诊断 |
| 403 | User.Indebt | Insufficient account balance. Please add funds. | 您已欠费，请充值。 | 诊断 |
| 403 | User.StatusInvalid | Abnormal account status. Check whether DFS has been activated for the account or whether the account has an outstanding payment. If the issue persists, submit a ticket. | 账号状态异常。请检查是否开通DFS服务，是否欠费。如仍未解决，请提交工单。 | 诊断 |
| 403 | VscMountPoint.HasInstance | The VSC mount point contains an ECS instance and cannot be deleted. | 当前VSC挂载点下存在ECS实例，无法删除。 | 诊断 |
| 403 | VscMountPoint.NotFound | The VSC mount point does not exist. | Vsc挂载点不存在 | 诊断 |
| 500 | InternalError.VscServerError | %s. | VSC（虚拟存储通道）服务端错误。DFS 管控调用 VSC 服务时 VSC 返回异常，具体原因见错误信息。建议先重试，若持续失败请联系支持。 | 诊断 |
该文章对您有帮助吗？