Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. NFS sharing type resources don't come online after the Cluster service fails over a cluster group in Windows Server 2008 R2 SP1

NFS sharing type resources don't come online after the Cluster service fails over a cluster group in Windows Server 2008 R2 SP1

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You create a Windows Server 2008 R2 Service Pack 1 (SP1)-based failover cluster.
  • You create a group in the cluster, and then you create more than 10 NFS sharing type resources in the group.
  • Resources in the group go offline, and then the Cluster service fails over the group to another node.

In this situation, not all the NFS sharing type resources come online on the destination node. Additionally, the following error is logged in Event Viewer:

There was a sharing violation of a particular resource. Please try again after some time or contact your administrator.

↑ Back to the top

More Information

This issue typically occurs when you have more than 10 NFS sharing type resources. However, the precise number of resources that cause the issue depends on the computer load and configuration.

After you install this hotfix, follow these steps:
  1. Open the PowerShell command prompt in administrator mode.
  2. Run the import-module failoverclusters command to enable cluster cmdlets.
  3. Change the values of the pendingTimeout and deadlockTimeout properties to 10 minutes as follows:
    (Get-ClusterResourceType "NFS share").pendingTimeout=600000  // miliseconds
    -and-
    (Get-ClusterResourceType "NFS share").deadlockTimeout=600000
  4. Check that the new values are applied correctly.

↑ Back to the top

Resolution

Hotfix information

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 website:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

To apply this hotfix, you must be running the following operating system:
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You might have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global 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
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    1.22xxx    		Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • 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" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. 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
File nameFile versionFile sizeDateTimePlatform
Nfssh.dll6.1.7601.2247651,2009-Oct-1313:45x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Nfssh.dll6.1.7601.22476112,1289-Oct-1312:52IA-64

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File propertyValue
File nameAmd64_00ec3ee7707ec3b94bdca117d4ee6b42_31bf3856ad364e35_6.1.7601.22476_none_2dba3ae49536139e.manifest
File versionNot applicable
File size714
Date (UTC)10-Oct-13
Time (UTC)5:08
PlatformNot applicable
File nameAmd64_microsoft-windows-nfs-server-clustercore_31bf3856ad364e35_6.1.7601.22476_none_2523450aabd02309.manifest
File versionNot applicable
File size3,867
Date (UTC)9-Oct-13
Time (UTC)14:16
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File propertyValue
File nameIa64_d04812bc36ab651370a0b0fc56b15324_31bf3856ad364e35_6.1.7601.22476_none_ab044ba3af363fd5.manifest
File versionNot applicable
File size712
Date (UTC)10-Oct-13
Time (UTC)5:08
PlatformNot applicable
File nameIa64_microsoft-windows-nfs-server-clustercore_31bf3856ad364e35_6.1.7601.22476_none_c9064d7cf370bacf.manifest
File versionNot applicable
File size3,865
Date (UTC)9-Oct-13
Time (UTC)13:21
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2897770
Revision : 1
Created on : 1/7/2017
Published on : 5/27/2014
Exists online : False
Views : 179