You enable the Cluster Shared Volumes feature on a cluster node that is running Windows Server 2008 R2.
You add an iSCSI disk or a fibre channel (FC) disk to the Cluster Shared Volumes list.
You set the disk to enter the volume maintenance mode and then set it to exit the volume maintenance mode.
In this scenario,you encounter one or more of the following problems:
If the disk is an FC disk, you cannot take this disk offline.
If the disk is an iSCSI disk, you cannot log off the session for this disk or take this disk offline. Additionally, you receive the following error message:
The session cannot be logged out since a device on that session is currently being used.
Also, the following event is added to the System log if the disk is an iSCSI disk:
Log Name: System Date: <date> Source: MSiSCSI Event ID: 116 Task Category: None Level: Information Keywords: Classic User: N/A Computer: <computer name> Description: Removal of device <device name> was vetoed by <name>
This issue occurs because the Cluster service does not free up some device handles.
When a disk is added to the Cluster Shared Volumes list, the Cluster service opens a handle to the disk device and then assigns an 8-byte persistent reservation key to each cluster node. However, the Cluster service does not free the device handles. Therefore, you encounter this issue.
To resolve this issue, install hotfix 979710 on the affected nodes that are running Windows Server 2008 R2.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must be running Windows Server 2008 R2.
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
For all supported IA-64-based versions of Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to deploy Cluster Shared Volumes for high-availability clustering in Windows Server 2008 R2, visit the following Microsoft website: