Export (0) Print
Expand All

Cluster Shared Volume Functionality

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

In a failover cluster, virtual machines can use Cluster Shared Volumes that are on the same LUN (disk), while still being able to fail over (or move from node to node) independently of one another. Virtual machines can use a Cluster Shared Volume only when communication between the cluster nodes and the volume is functioning correctly, including network connectivity, access, drivers, and other factors.

Events

Event ID Source Message

5120

Microsoft-Windows-FailoverClustering

Cluster Shared Volume '%1' ('%2') is no longer available on this node because of '%3'. All I/O will temporarily be queued until a path to the volume is reestablished.

5121

Microsoft-Windows-FailoverClustering

Cluster Shared Volume '%1' ('%2') is no longer directly accessible from this cluster node. I/O access will be redirected to the storage device over the network through the node that owns the volume. This may result in degraded performance. If redirected access is turned on for this volume, please turn it off. If redirected access is turned off, please troubleshoot this node's connectivity to the storage device and I/O will resume to a healthy state once connectivity to the storage device is reestablished.

5123

Microsoft-Windows-FailoverClustering

Cluster service failed to create the Cluster Shared Volumes root directory '%2'. The error message was '%1'.

5124

Microsoft-Windows-FailoverClustering

Cluster Shared Volumes root directory '%1' already exists. The directory '%1' was renamed to '%2'. Please verify that applications accessing data in this location have been updated as necessary.

5125

Microsoft-Windows-FailoverClustering

Cluster Shared Volume '%1' ('%3') has identified one or more active filter drivers on this device stack that could interfere with CSV operations. I/O access will be redirected to the storage device over the network through another Cluster node. This may result in degraded performance. Please contact the filter driver vendor to verify interoperability with Cluster Shared Volumes.

Active filter drivers found:
%2

5126

Microsoft-Windows-FailoverClustering

Cluster Shared Volume '%1' ('%3') has identified one or more active volume drivers on this device stack that could interfere with CSV operations. I/O access will be redirected to the storage device over the network through another Cluster node. This may result in degraded performance. Please contact the volume driver vendor to verify interoperability with Cluster Shared Volumes.

Active volume drivers found:
%2

5128

Microsoft-Windows-FailoverClustering

Physical disk resource '%1' does not allow disabling short name generation. This may cause application compatibility issues. Please use 'fsutil 8dot3name set 2' to allow disabling short name generation and then offline/online the resource.

5133

Microsoft-Windows-FailoverClustering

Cluster Disk '%1' has been removed and placed back in the 'Available Storage' cluster group. During this process an attempt to restore the original drive letter(s) has taken longer than expected, possibly due to those drive letters being already in use.

5134

Microsoft-Windows-FailoverClustering

Cluster service failed to set the permissions (ACL) on the Cluster Shared Volumes root directory '%1'. The error was '%2'.

5135

Microsoft-Windows-FailoverClustering

Cluster service failed to set the permissions on the Cluster Shared Volume directory '%1' ('%2'). The error was '%3'.

5136

Microsoft-Windows-FailoverClustering

Cluster Shared Volume '%1' ('%2') redirected access was turned on. Access to the storage device will be redirected over the network from all cluster nodes that are accessing this volume. This may result in degraded performance. Please turn off redirected access for this volume.

5142

Microsoft-Windows-FailoverClustering

Cluster Shared Volume '%1' ('%2') is no longer accessible from this cluster node because of error '%3'. Please troubleshoot this node's connectivity to the storage device and network connectivity.

5200

Microsoft-Windows-FailoverClustering

Cluster service failed to create a cluster identity token for Cluster Shared Volumes. The error code was '%1'. Ensure the domain controller is accessible and check for connectivity issues. Until connection to the domain controller is recovered, some operations on this node against the Cluster Shared Volumes might fail.

Related Management Information

Cluster Shared Volumes

Failover Clustering

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft