Translations by Cristina Xu
Cristina Xu has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 3. |
An unknown exception occurred.
|
|
| 2016-08-24 |
發生一個未知例外。
|
|
| 9. |
Not authorized.
|
|
| 2016-08-24 |
未被授權。
|
|
| 10. |
User does not have admin privileges
|
|
| 2016-08-24 |
使用者並沒有管理者專用權
|
|
| 42. |
Volume Type %(volume_type_id)s deletion is not allowed with volumes present with the type.
|
|
| 2016-08-24 |
磁區類型 %(volume_type_id)s 刪除作業不為該類型的磁區所接受。
|
|
| 72. |
Quota exceeded: code=%(code)s
|
|
| 2016-08-24 |
已超出配額：錯誤碼為 %(code)s
|
|
| 80. |
Operation failed with status=%(status)s. Full dump: %(data)s
|
|
| 2016-08-24 |
作業失敗，狀態為 %(status)s。完整傾出：%(data)s
|
|
| 104. |
Failed to associate qos_specs: %(specs_id)s with type %(type_id)s.
|
|
| 2016-08-24 |
無法使 qos_specs：%(specs_id)s 與類型 %(type_id)s 關聯。
|
|
| 110. |
Manage existing volume failed due to invalid backend reference %(existing_ref)s: %(reason)s
|
|
| 2016-08-24 |
管理現有磁區時失敗，因為後端參照 %(existing_ref)s 無效：%(reason)s
|
|
| 128. |
Error in SolidFire API response: data=%(data)s
|
|
| 2016-08-24 |
SolidFire API 回應發生錯誤：資料為 %(data)s
|
|
| 177. |
%(name)s has a minimum character requirement of %(min_length)s.
|
|
| 2016-08-24 |
%(name)s 具有字元數目下限要求 %(min_length)s。
|
|
| 178. |
%(name)s has more than %(max_length)s characters.
|
|
| 2016-08-24 |
%(name)s 具有超過 %(max_length)s 個字元。
|
|
| 255. |
Provided snapshot status %(provided)s not allowed for snapshot with status %(current)s.
|
|
| 2016-08-24 |
提供的 Snapshot 狀態 %(provided)s，不為 Snapshot（狀態為 %(current)s）所接受。
|
|
| 312. |
too many body keys
|
|
| 2016-08-24 |
主體索引鍵太多
|
|
| 391. |
Restore backup aborted, the backup service currently configured [%(configured_service)s] is not the backup service that was used to create this backup [%(backup_service)s].
|
|
| 2016-08-24 |
已中止還原備份，目前配置的備份服務 [%(configured_service)s] 不是建立此備份所使用的備份服務 [%(backup_service)s]。
|
|
| 395. |
Delete backup aborted, the backup service currently configured [%(configured_service)s] is not the backup service that was used to create this backup [%(backup_service)s].
|
|
| 2016-08-24 |
已中止刪除備份，目前配置的備份服務 [%(configured_service)s] 不是建立此備份所使用的備份服務 [%(backup_service)s]。
|
|
| 399. |
Export record aborted, the backup service currently configured [%(configured_service)s] is not the backup service that was used to create this backup [%(backup_service)s].
|
|
| 2016-08-24 |
已中止匯出記錄，目前配置的備份服務 [%(configured_service)s] 不是建立此備份所使用的備份服務 [%(backup_service)s]。
|
|
| 435. |
Snapshot='%(snap)s' does not exist in base image='%(base)s' - aborting incremental backup
|
|
| 2016-08-24 |
基本映像檔 '%(base)s' 中不存在 Snapshot '%(snap)s' - 正在中止增量備份
|
|
| 506. |
%(op)s: backup %(bck_id)s, volume %(vol_id)s failed. Backup object has unexpected mode. Image or file backups supported, actual mode is %(vol_mode)s.
|
|
| 2016-08-24 |
%(op)s：備份 %(bck_id)s，磁區 %(vol_id)s 失敗。備份物件具有非預期的模式。支援映像檔或檔案備份，實際模式為 %(vol_mode)s。
|
|
| 507. |
backup: %(vol_id)s failed to create device hardlink from %(vpath)s to %(bpath)s.
stdout: %(out)s
stderr: %(err)s
|
|
| 2016-08-24 |
備份：%(vol_id)s 無法建立從 %(vpath)s 到 %(bpath)s 的裝置固定鏈結。
標準輸出：%(out)s
標準錯誤：%(err)s
|
|
| 517. |
backup: %(vol_id)s failed to run dsmc due to invalid arguments on %(bpath)s.
stdout: %(out)s
stderr: %(err)s
|
|
| 2016-08-24 |
備份：%(vol_id)s 無法執行 dsmc，因為 %(bpath)s 的引數無效。
標準輸出：%(out)s
標準錯誤：%(err)s
|
|
| 521. |
restore: %(vol_id)s failed to run dsmc due to invalid arguments on %(bpath)s.
stdout: %(out)s
stderr: %(err)s
|
|
| 2016-08-24 |
還原：%(vol_id)s 無法執行 dsmc，因為 %(bpath)s 上的引數無效。
標準輸出：%(out)s
標準錯誤：%(err)s
|
|
| 604. |
Unknown sort direction, must be 'desc' or 'asc'
|
|
| 2016-08-24 |
不明的排序方向，必須為「降序」或「升序」
|
|
| 617. |
Transfer %(transfer_id)s: Volume id %(volume_id)s in unexpected state %(status)s, expected awaiting-transfer
|
|
| 2016-08-24 |
傳送 %(transfer_id)s：磁區 ID %(volume_id)s 處於非預期的狀態 %(status)s，預期狀態為 awaiting-transfer
|
|
| 652. |
fmt=%(fmt)s backed by: %(backing_file)s
|
|
| 2016-08-24 |
fmt %(fmt)s 受 %(backing_file)s 支援
|
|
| 653. |
Size is %(image_size)dGB and doesn't fit in a volume of size %(volume_size)dGB.
|
|
| 2016-08-24 |
大小為 %(image_size)dGB，無法容納大小為 %(volume_size)dGB 的磁區。
|
|
| 655. |
qemu-img is not installed and the disk format is not specified. Only RAW images can be used if qemu-img is not installed.
|
|
| 2016-08-24 |
未安裝 qemu-img，且未指定磁碟格式。如果未安裝 qemu-img，則只能使用原始映像檔。
|
|
| 740. |
Invalid value for 'scheduler_max_attempts', must be >=1
|
|
| 2016-08-24 |
'scheduler_max_attempts' 的值無效，必須大於或等於 1
|
|
| 750. |
Failed to create scheduler manager volume flow
|
|
| 2016-08-24 |
無法建立排程器管理程式磁區流程
|
|
| 769. |
Failed to backup volume metadata - Metadata backup object 'backup.%s.meta' already exists
|
|
| 2016-08-24 |
無法備份磁區 meta 資料 - meta 資料備份物件 'backup.%s.meta' 已存在
|
|
| 772. |
Error not a TypeError.
|
|
| 2016-03-25 |
此錯誤不是 TypeError。
|
|
| 773. |
Error not a KeyError.
|
|
| 2016-03-25 |
此錯誤不是 KeyError。
|
|
| 830. |
Volume status is in-use.
|
|
| 2016-08-24 |
磁區狀態為「使用中」。
|
|
| 944. |
Type %(type_id)s is already associated with another qos specs: %(qos_specs_id)s
|
|
| 2016-08-24 |
類型 %(type_id)s 已經與另一個服務品質規格 %(qos_specs_id)s 產生關聯
|
|
| 1002. |
Volume status must be "available" or "in-use" for snapshot. (is %s)
|
|
| 2016-08-24 |
對於 Snapshot，磁區狀態必須為「可用」或「使用中」。（磁區狀態目前是 %s）
|
|
| 1035. |
Backup is only supported for raw-formatted GlusterFS volumes.
|
|
| 2016-08-24 |
僅原始格式的 GlusterFS 磁區僅支援備份。
|
|
| 1043. |
Failed to manage existing volume %(name)s, because reported size %(size)s was not a floating-point number.
|
|
| 2016-08-24 |
無法管理現有磁區 %(name)s，因為所報告的大小 %(size)s 不是浮點數字。
|
|
| 1061. |
rados and rbd python libraries not found
|
|
| 2016-08-24 |
找不到 rados 及 rbd Python 程式庫
|
|
| 1474. |
The GPFS filesystem %(fs)s is not at the required release level. Current level is %(cur)s, must be at least %(min)s.
|
|
| 2016-08-24 |
GPFS 檔案系統 %(fs)s 不是必要的版次。現行發行層次是 %(cur)s，必須至少是 %(min)s。
|
|
| 1573. |
Mapping %(id)s prepare failed to complete within theallotted %(to)d seconds timeout. Terminating.
|
|
| 2016-08-24 |
無法在所分配的 %(to)d 秒逾時時間內完成對映 %(id)s準備。正在終止。
|
|
| 1596. |
No element by given name %s.
|
|
| 2016-03-25 |
依給定的名稱 %s，找不到元素。
|
|
| 1597. |
Not a valid value for NaElement.
|
|
| 2016-03-25 |
不是 NaElement 的有效值。
|
|
| 1598. |
NaElement name cannot be null.
|
|
| 2016-03-25 |
NaElement 名稱不能是空值。
|
|
| 1599. |
Type cannot be converted into NaElement.
|
|
| 2016-03-25 |
無法將類型轉換為 NaElement。
|
|
| 1746. |
Requires an NaServer instance.
|
|
| 2016-03-25 |
需要 NaServer 實例。
|
|
| 1749. |
Invalid transport type.
|
|
| 2016-03-25 |
傳輸類型無效。
|
|
| 1751. |
Invoking web service failed.
|
|
| 2016-03-25 |
呼叫 Web 服務失敗。
|
|
| 1803. |
Volume %s does not exist in Nexenta SA
|
|
| 2016-03-25 |
磁區 %s 不存在於 Nexenta SA 中
|
|
| 1829. |
Volume %s does not exist in Nexenta Store appliance
|
|
| 2016-03-25 |
磁區 %s 不存在於「Nexenta 儲存庫」軟體驅動裝置中
|
|
| 1830. |
Folder %s does not exist in Nexenta Store appliance
|
|
| 2016-03-25 |
資料夾 %s 不存在於「Nexenta 儲存庫」軟體驅動裝置中
|
|
| 1840. |
Invalid value: "%s"
|
|
| 2016-03-25 |
無效的值："%s"
|
|
