Event ID 5128 — Cluster Shared Volume Functionality
Applies To: Windows Server 2008 R2
.jpg)
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.
Event Details
| Product: | Windows Operating System |
| ID: | 5128 |
| Source: | Microsoft-Windows-FailoverClustering |
| Version: | 6.1 |
| Symbolic Name: | DCM_EVENT_CANNOT_DISABLE_SHORT_NAMES |
| Message: | 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. |
Resolve
CSV - Check volume setting for short name generation
Cluster Shared Volumes has detected that on the node on which the event was logged, short name generation (for the file system) cannot be disabled. This does not interfere with Cluster Shared Volumes, but it could interfere with the function of some applications. For best results, configure the node to allow disabling of short name generation. For more information, see "Configuring the short name generation setting."
If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering."
To perform the following procedure, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.
Configuring the short name generation setting
To configure the short name generation setting:
On the node where you want to configure the setting, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type:
fsutil 8dot3name set 2
To confirm the setting, type:
fsutil 8dot3name query
Text similar to the following should be displayed:
The registry state of NtfsDisable8dot3NameCreation is 2, the default (Volume level setting).
To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
In the Failover Cluster Manager snap-in, expand the console tree and click Cluster Shared Volumes. In the center pane, expand the listing for the disk affected by the short name generation setting. View the status of the volume.
Still in the center pane, right-click the disk, and then click Take this resource offline. If prompted, confirm your choice.
Still in the center pane, right-click the disk, and then click Bring this resource online.
Opening Event Viewer and viewing events related to failover clustering
To open Event Viewer and view events related to failover clustering:
- If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
- To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
- To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.
Verify
Confirm that the Cluster Shared Volume can come online. If there have been recent problems with writing to the volume, it can be appropriate to monitor event logs and monitor the function of the corresponding clustered virtual machine, to confirm that the problems have been resolved.
To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.
Confirming that a Cluster Shared Volume can come online
To confirm that a Cluster Shared Volume can come online:
- To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
- In the Failover Cluster Manager snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
- If the console tree is collapsed, expand the tree under the cluster you want to manage, and then click Cluster Shared Volumes.
- In the center pane, expand the listing for the volume that you are verifying. View the status of the volume.
- If a volume is offline, to bring it online, right-click the volume and then click Bring this resource online.
Using a Windows PowerShell command to check the status of a resource in a failover cluster
To use a Windows PowerShell command to check the status of a resource in a failover cluster:
On a node in the cluster, click Start, point to Administrative Tools, and then click Windows PowerShell Modules. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
Type:
Get-ClusterSharedVolume
If you run the preceding command without specifying a resource name, status is displayed for all Cluster Shared Volumes in the cluster.