Symptoms
Consider the following scenario:
-
You have a network file system (NFS) share on a Windows Server 2008-based NFS server.
-
You use a UNIX client that does not support 64-bit cookies to access files in the NFS share.
-
You try to perform a file operation from the UNIX client. For example, you try to run the tar command to archive files, or you try to run the ls command to list files in a directory.
In this scenario, the file operation fails. For example, duplicate file names are displayed or the command falls in to an infinite loop.
Cause
This issue occurs because duplicate cookies are generated and returned to the UNIX client by the NFS server.Note In a directory that contains many New Technology File System (NTFS) hard links to the same file, duplicate cookie issues can occur. To avoid duplicate cookie issues, NFS server uses file name hashing in the cookie generating algorithm. This may result in duplicate cookies when many files have similar file names in a NFS share.
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=supportNote 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 Windows Server 2008 Service Pack 2 (SP2).For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849How to obtain the latest service pack for Windows Server 2008
Registry information
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in WindowsAfter apply this hotfix, you must create a registry key to disable file name hashing for cookies on NFS version 2 server or NFS version 3 server. To do this, follow these steps:
-
Click Start
-
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NfsServer\Parameters
-
On the Edit menu, point to New, and then click DWORD Value.
-
Type DisableFilenameHashing, and then press ENTER.
-
Right-click DisableFilenameHashing, and then click Modify.
-
In the Value data box, type 1, and then click OK.
-
Exit Registry Editor.
Notes
-
You can use the DisableFilenameHashing registry entry to control if the file name hashing is used or not when NFS server generates cookies. You can set the DWORD value of the DisableFilenameHashing registry entry to 0 to enable the file name hashing.
-
Please do not disable the file name hashing if the NFS share contains many NFS hard links that point to the same file.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 file information notesImportant Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
SR_Level
Service branch
6.0.600 2. 22xxx
Windows Server 2008
SP2
LDR
-
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" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important 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 x86-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Msnfsflt.mof |
Not applicable |
4,437 |
09-Sep-2011 |
11:48 |
Not applicable |
|
Msnfsflt.sys |
6.0.6002.23087 |
23,552 |
06-Apr-2013 |
01:18 |
x86 |
|
Nfs-servercore-ppdlic.xrm-ms |
Not applicable |
3,001 |
06-Apr-2013 |
02:34 |
Not applicable |
|
Nfssvc.exe |
6.0.6002.23087 |
28,672 |
06-Apr-2013 |
01:18 |
x86 |
|
Nfssvr.mof |
Not applicable |
6,172 |
09-Sep-2011 |
11:48 |
Not applicable |
|
Nfssvr.sys |
6.0.6002.23087 |
498,176 |
06-Apr-2013 |
01:19 |
x86 |
For all supported x64-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Msnfsflt.mof |
Not applicable |
4,437 |
01-Dec-2011 |
11:39 |
Not applicable |
|
Msnfsflt.sys |
6.0.6002.23087 |
30,208 |
06-Apr-2013 |
01:58 |
x64 |
|
Nfs-servercore-ppdlic.xrm-ms |
Not applicable |
3,001 |
06-Apr-2013 |
03:25 |
Not applicable |
|
Nfssvc.exe |
6.0.6002.23087 |
33,280 |
06-Apr-2013 |
01:58 |
x64 |
|
Nfssvr.mof |
Not applicable |
6,172 |
01-Dec-2011 |
11:39 |
Not applicable |
|
Nfssvr.sys |
6.0.6002.23087 |
644,096 |
06-Apr-2013 |
01:59 |
x64 |
For all supported IA-64-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Msnfsflt.mof |
Not applicable |
4,437 |
15-Mar-2011 |
06:04 |
Not applicable |
|
Msnfsflt.sys |
6.0.6002.23087 |
65,024 |
06-Apr-2013 |
00:58 |
IA-64 |
|
Nfs-servercore-ppdlic.xrm-ms |
Not applicable |
3,001 |
06-Apr-2013 |
02:14 |
Not applicable |
|
Nfssvc.exe |
6.0.6002.23087 |
67,584 |
06-Apr-2013 |
00:58 |
IA-64 |
|
Nfssvr.mof |
Not applicable |
6,172 |
15-Mar-2011 |
06:04 |
Not applicable |
|
Nfssvr.sys |
6.0.6002.23087 |
1,412,608 |
06-Apr-2013 |
00:59 |
IA-64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
