分布式卷
分布式卷是 DVM(分布式卷管理器)的界面,一个导航条目下包含四个视图。卷列表显示每个卷的存储类别(临时、复制、共享或对象)以及生命周期阶段——就绪、同步中、迁移中、降级等;卷详情视图深入展示单个卷的每个副本状态以及跨节点进行中的迁移。网格状态报告 WireGuard 网格对等连接性以及 DVM 所运行的 SeaweedFS/MinIO 存储后端的健康状况。建议页面呈现存储类别、副本数量、容量和成本建议,每条建议都按优先级排序,并说明平台是否能为你执行该建议或无法执行的原因。
如何到达此处
Section titled “如何到达此处”侧边栏部分 主菜单 → 分布式卷。

/dvm/mesh (DVMMeshStatus)
Section titled “/dvm/mesh (DVMMeshStatus)”infrastructure:dVMMeshStatus.allowed-ips— “允许的 IP”infrastructure:dVMMeshStatus.back-to-volumes— “返回卷”infrastructure:dVMMeshStatus.buckets— “存储桶”infrastructure:dVMMeshStatus.connected-peers— “已连接对等节点”infrastructure:dVMMeshStatus.data-received— “已接收数据”infrastructure:dVMMeshStatus.data-sent— “已发送数据”infrastructure:dVMMeshStatus.degraded— “已降级”infrastructure:dVMMeshStatus.disabled— “已禁用”infrastructure:dVMMeshStatus.dvm-infrastructure— “DVM 基础设施”infrastructure:dVMMeshStatus.dvm-infrastructure-services-are-not— “此租户的 DVM 基础设施服务尚未配置。”infrastructure:dVMMeshStatus.enabled— “已启用”infrastructure:dVMMeshStatus.endpoint— “端点”infrastructure:dVMMeshStatus.free— “免费)”infrastructure:dVMMeshStatus.healthy— “健康”infrastructure:dVMMeshStatus.last-handshake— “上次握手”infrastructure:dVMMeshStatus.latency— “延迟”infrastructure:dVMMeshStatus.listen-port— “监听端口”infrastructure:dVMMeshStatus.loading— “加载中…”infrastructure:dVMMeshStatus.local-node— “本地节点”infrastructure:dVMMeshStatus.master— “主节点”infrastructure:dVMMeshStatus.minio-not-configured— “MinIO 未配置”infrastructure:dVMMeshStatus.minio-object-storage— “MinIO(对象存储)”infrastructure:dVMMeshStatus.never— “从不”infrastructure:dVMMeshStatus.no-infrastructure-configured— “未配置基础设施”infrastructure:dVMMeshStatus.node— “节点”infrastructure:dVMMeshStatus.node-id— “节点 ID”infrastructure:dVMMeshStatus.not-available— “不可用”infrastructure:dVMMeshStatus.peer-details— “对等节点详情:”infrastructure:dVMMeshStatus.public-key— “公钥”infrastructure:dVMMeshStatus.received— “已接收”infrastructure:dVMMeshStatus.refresh— “刷新”infrastructure:dVMMeshStatus.seaweedfs-not-configured— “SeaweedFS 未配置”infrastructure:dVMMeshStatus.seaweedfs-shared-storage— “SeaweedFS(共享存储)”infrastructure:dVMMeshStatus.sent— “已发送”infrastructure:dVMMeshStatus.status— “状态”infrastructure:dVMMeshStatus.storage-used— “已用存储”infrastructure:dVMMeshStatus.transfer— “传输”infrastructure:dVMMeshStatus.unhealthy— “不健康”infrastructure:dVMMeshStatus.unknown— “未知”infrastructure:dVMMeshStatus.volumes— “卷”infrastructure:dVMMeshStatus.wireguard-mesh— “WireGuard 网格”infrastructure:dVMMeshStatus.wireguard-mesh-network-and-storage— “WireGuard 网格网络与存储服务状态”infrastructure:dVMMeshStatus.wireguard-mesh-not-configured— “WireGuard 网格未配置”infrastructure:dVMMeshStatus.wireguard-peers— “WireGuard 对等节点”
/dvm/recommendations (DVMRecommendations)
Section titled “/dvm/recommendations (DVMRecommendations)”infrastructure:dVMRecommendations.acknowledge— “确认”infrastructure:dVMRecommendations.acknowledge-but-dont-apply— “确认但不应用”infrastructure:dVMRecommendations.acknowledged— “已确认”infrastructure:dVMRecommendations.active-recommendations— “活跃建议”infrastructure:dVMRecommendations.all-priorities— “所有优先级”infrastructure:dVMRecommendations.all-types— “所有类型”infrastructure:dVMRecommendations.apply— “应用”infrastructure:dVMRecommendations.apply-this-recommendation— “应用此建议”infrastructure:dVMRecommendations.back-to-volumes— “返回卷”infrastructure:dVMRecommendations.capacity— “容量”infrastructure:dVMRecommendations.clear-filters— “清除筛选器”infrastructure:dVMRecommendations.collapse— “折叠”infrastructure:dVMRecommendations.cost-optimization— “成本优化”infrastructure:dVMRecommendations.created— “创建时间:”infrastructure:dVMRecommendations.critical— “严重”infrastructure:dVMRecommendations.dismiss— “忽略”infrastructure:dVMRecommendations.dvm-recommendations— “DVM 建议”infrastructure:dVMRecommendations.expand— “展开”infrastructure:dVMRecommendations.great-job-your-volumes-are— “干得好!您的卷已优化配置。”infrastructure:dVMRecommendations.high— “高”infrastructure:dVMRecommendations.high-priority— “高优先级”infrastructure:dVMRecommendations.loading-recommendations— “正在加载建议…”infrastructure:dVMRecommendations.low— “低”infrastructure:dVMRecommendations.medium— “中”infrastructure:dVMRecommendations.no-recommendations— “无建议”infrastructure:dVMRecommendations.no-recommendations-match-your-filters— “没有符合您筛选条件的建议。”infrastructure:dVMRecommendations.optimize-your-distributed-volumes— “根据您的卷的实时大小、副本和快照状态计算出的建议”infrastructure:dVMRecommendations.parameters— “参数”infrastructure:dVMRecommendations.potential-monthly-savings— “潜在月度节省”infrastructure:dVMRecommendations.recommended-action— “建议操作”infrastructure:dVMRecommendations.refresh— “刷新”infrastructure:dVMRecommendations.replica-count— “副本数”infrastructure:dVMRecommendations.show-acknowledged— “显示已确认”infrastructure:dVMRecommendations.storage-class— “存储类”infrastructure:dVMRecommendations.view-volume— “查看卷 →”
/dvm/volumes (DVMVolumes)
Section titled “/dvm/volumes (DVMVolumes)”infrastructure:dVMVolumes.access-mode— “访问模式”infrastructure:dVMVolumes.access-mode-rox— “ReadOnlyMany — 多个节点以只读方式挂载”infrastructure:dVMVolumes.access-mode-rwo— “ReadWriteOnce — 一个节点以读写方式挂载”infrastructure:dVMVolumes.access-mode-rwx— “ReadWriteMany — 多个节点以读写方式挂载(共享类)”infrastructure:dVMVolumes.actions— “操作”infrastructure:dVMVolumes.all-classes— “所有类”infrastructure:dVMVolumes.all-data-on-this-volume— “此卷及其副本上的所有数据将被永久删除。”infrastructure:dVMVolumes.all-phases— “所有阶段”infrastructure:dVMVolumes.are-you-sure-you-want— “您确定要删除该卷吗”infrastructure:dVMVolumes.cancel— “取消”infrastructure:dVMVolumes.class— “类”infrastructure:dVMVolumes.class-2— “| 类:”infrastructure:dVMVolumes.clear-filters— “清除过滤器”infrastructure:dVMVolumes.create-distributed-volume— “创建分布式卷”infrastructure:dVMVolumes.create-volume— “创建卷”infrastructure:dVMVolumes.creating— “创建中…”infrastructure:dVMVolumes.degraded-failed— “降级/失败”infrastructure:dVMVolumes.delete— “删除”infrastructure:dVMVolumes.delete-volume— “删除卷”infrastructure:dVMVolumes.deleting— “删除中…”infrastructure:dVMVolumes.details— “详情”infrastructure:dVMVolumes.distributed-volumes— “分布式卷”infrastructure:dVMVolumes.enable-compression— “启用压缩”infrastructure:dVMVolumes.ephemeral— “临时”infrastructure:dVMVolumes.ephemeral-local-only— “临时(仅限本地)”infrastructure:dVMVolumes.failover-auto— “自动”infrastructure:dVMVolumes.failover-auto-explain— “当主节点失效时,一个经过验证的新副本将被提升,无需等待。如果没有足够新的副本,故障转移将等待您的批准,而不是提升过时的数据。”infrastructure:dVMVolumes.failover-manual— “手动”infrastructure:dVMVolumes.failover-manual-explain— “提升操作始终等待操作员的批准,即使副本是新的。”infrastructure:dVMVolumes.failover-policy— “故障转移策略”infrastructure:dVMVolumes.get-started-by-creating-a— “通过创建新的分布式卷开始。”infrastructure:dVMVolumes.healthy— “健康”infrastructure:dVMVolumes.loading-volumes— “正在加载卷…”infrastructure:dVMVolumes.mesh-status— “网格状态”infrastructure:dVMVolumes.name— “名称”infrastructure:dVMVolumes.no-volumes-found— “未找到卷”infrastructure:dVMVolumes.object— “对象”infrastructure:dVMVolumes.object-minio-s3— “对象 (MinIO S3)”infrastructure:dVMVolumes.pending-approvals-title— “等待批准的卷故障转移”infrastructure:dVMVolumes.phase— “阶段”infrastructure:dVMVolumes.primary— “主节点”infrastructure:dVMVolumes.ready— “就绪”infrastructure:dVMVolumes.replica-count— “副本数”infrastructure:dVMVolumes.replicas— “副本”infrastructure:dVMVolumes.replicas-2— “| 副本数:”infrastructure:dVMVolumes.replicated— “已复制”infrastructure:dVMVolumes.replicated-async-rsync— “已复制 (异步 rsync)”infrastructure:dVMVolumes.review-and-approve— “审核并批准 →”infrastructure:dVMVolumes.shared— “共享”infrastructure:dVMVolumes.shared-seaweedfs— “共享 (SeaweedFS)”infrastructure:dVMVolumes.size— “大小”infrastructure:dVMVolumes.size-2— “大小:”infrastructure:dVMVolumes.size-gb— “大小 (GB)”infrastructure:dVMVolumes.storage-class— “存储类”infrastructure:dVMVolumes.sync-interval-seconds— “同步间隔(秒)”infrastructure:dVMVolumes.this-action-cannot-be-undone— “此操作无法撤销”infrastructure:dVMVolumes.total-capacity— “总容量”infrastructure:dVMVolumes.total-volumes— “总卷数”infrastructure:dVMVolumes.unhealthy— “不健康”infrastructure:dVMVolumes.used— “已使用”infrastructure:dVMVolumes.view-recommendations— “查看建议”infrastructure:dVMVolumes.volume-name— “卷名称 *”infrastructure:dVMVolumes.volumes— “卷”
/dvm/volumes/:volumeId (DVMVolumeDetail)
Section titled “/dvm/volumes/:volumeId (DVMVolumeDetail)”infrastructure:dVMVolumeDetail.access-mode— “访问模式”infrastructure:dVMVolumeDetail.approve-title— “批准陈旧提升”infrastructure:dVMVolumeDetail.back-to-volumes— “← 返回卷”infrastructure:dVMVolumeDetail.cancel— “取消”infrastructure:dVMVolumeDetail.cancel-migration— “取消迁移”infrastructure:dVMVolumeDetail.complete— “% 完成”infrastructure:dVMVolumeDetail.compression— “压缩”infrastructure:dVMVolumeDetail.confirm-failover— “确认故障转移”infrastructure:dVMVolumeDetail.created— “创建”infrastructure:dVMVolumeDetail.disabled— “已禁用”infrastructure:dVMVolumeDetail.enabled— “已启用”infrastructure:dVMVolumeDetail.encryption-at-rest— “静态加密”infrastructure:dVMVolumeDetail.eta— “| 预计剩余时间:”infrastructure:dVMVolumeDetail.failing-over— “正在故障转移…”infrastructure:dVMVolumeDetail.failover— “故障转移”infrastructure:dVMVolumeDetail.failover-policy— “故障转移策略”infrastructure:dVMVolumeDetail.failover-volume— “故障转移卷”infrastructure:dVMVolumeDetail.failover-will-immediately-promote-a— “故障转移将立即将一个副本提升为主副本。这适用于当前主副本不可用时的紧急情况。”infrastructure:dVMVolumeDetail.healthy— “健康”infrastructure:dVMVolumeDetail.id— “ID:”infrastructure:dVMVolumeDetail.in-sync— “同步中”infrastructure:dVMVolumeDetail.labels— “标签”infrastructure:dVMVolumeDetail.last-sync— “上次同步”infrastructure:dVMVolumeDetail.last-updated— “上次更新”infrastructure:dVMVolumeDetail.loading-volume-details— “正在加载卷详情…”infrastructure:dVMVolumeDetail.local-size— “本地大小”infrastructure:dVMVolumeDetail.migrate— “迁移”infrastructure:dVMVolumeDetail.migrate-volume— “迁移卷”infrastructure:dVMVolumeDetail.migration-in-progress— “迁移进行中”infrastructure:dVMVolumeDetail.no-replicas-configured— “未配置副本”infrastructure:dVMVolumeDetail.node— “节点”infrastructure:dVMVolumeDetail.path— “路径”infrastructure:dVMVolumeDetail.pending-approval-title— “故障转移等待批准”infrastructure:dVMVolumeDetail.primary-node— “主节点”infrastructure:dVMVolumeDetail.replicas— “副本”infrastructure:dVMVolumeDetail.role— “角色”infrastructure:dVMVolumeDetail.select-a-node— “选择一个节点…”infrastructure:dVMVolumeDetail.select-a-replica— “选择一个副本…”infrastructure:dVMVolumeDetail.select-a-target-node-to— “选择一个目标节点以迁移此卷的主副本。迁移将把数据同步到目标节点,然后切换主副本。”infrastructure:dVMVolumeDetail.size— “大小”infrastructure:dVMVolumeDetail.specification— “规格”infrastructure:dVMVolumeDetail.start-migration— “开始迁移”infrastructure:dVMVolumeDetail.starting— “正在启动…”infrastructure:dVMVolumeDetail.status— “状态”infrastructure:dVMVolumeDetail.sync-interval— “同步间隔”infrastructure:dVMVolumeDetail.sync-lag— “同步延迟”infrastructure:dVMVolumeDetail.target-node— “目标节点”infrastructure:dVMVolumeDetail.target-replica— “目标副本”infrastructure:dVMVolumeDetail.unhealthy— “不健康”infrastructure:dVMVolumeDetail.used— “已使用”infrastructure:dVMVolumeDetail.utilized— “% 已使用”infrastructure:dVMVolumeDetail.volume-not-found— “未找到卷”
/dvm/mesh
Section titled “/dvm/mesh”此屏幕的组件未声明任何权限控制。
/dvm/recommendations
Section titled “/dvm/recommendations”此屏幕的组件未声明任何权限控制。
/dvm/volumes
Section titled “/dvm/volumes”此屏幕的组件未声明任何权限控制。
/dvm/volumes/:volumeId
Section titled “/dvm/volumes/:volumeId”此屏幕的组件未声明任何权限控制。
请从分布式卷开始了解存储类和副本在此处的实际含义, 然后分布式卷了解将卷附加到部署的任务步骤。请参阅 卷屏幕了解更简单的单节点替代方案, 这并非该方案。