-
-
-
Selecting the write cache destination for standard vDisk images
-
Releasing vDisk locks
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Releasing vDisk locks
Multiple target devices and Citrix Provisioning servers access a single vDisk image file, which makes it necessary to control access to prevent corruption of the image. When a user accidentally assigns a private image to multiple target devices, and then tries to boot those target devices, a corrupt image results. Therefore, the image becomes locked appropriately for a given configuration. The locked vDisk icon appears with a small lock on it.
Under certain circumstances these locks are not released properly. A lock on a vDisk image is not released properly when:
- a target device machine is booted from a vDisk, and then
- shuts down without running through the normal shutdown process. For example, if the VM crashes or the hypervisor stops the VM without waiting for orderly shutdown to complete.
If the same target device boots again, the same lock is used and no problem occurs. However, if an administrator tries to mount the drive on the provisioning server after the target device has failed, the server fails to mount that vDisk. The server fails to mount the vDisk because a lock is still held by the failed target device. The administrator can release these locks.
Note:
Ensure that the vDisk is not in use before removing a lock. Removing a lock for a vDisk, which is in use, might corrupt the image.
To release vDisk locks
- In the Citrix Provisioning console, right-click on the vDisk for which you want to release locks, and then select the Manage Locks option. The Manage VDisk Locks dialog appears.
- If a vDisk has a target device lock on it, that target device name appears in the dialog’s list. Select one or more target devices from the list, then click Remove lock. You can also choose Select All to remove all target device locks on the selected vDisk.
- Click Close to close the dialog.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.