Ls command takes a long time to list shared files in two windows on a Windows-based NFS server

Applies To
Windows Server 2008 R2 Service Pack 1 Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Enterprise Windows Server 2008 R2 for Itanium-Based Systems Windows Server 2008 R2 Standard Windows 7 Service Pack 1 Windows 7 Ultimate Windows 7 Enterprise Windows 7 Professional Windows 7 Home Premium Windows 7 Home Basic Windows 7 Starter Windows Server 2008 Service Pack 2 Windows Server 2008 Datacenter Windows Server 2008 Enterprise Windows Server 2008 Standard Windows Server 2008 Foundation Windows Vista Service Pack 2 Windows Vista Ultimate Windows Vista Enterprise Windows Vista Business Windows Vista Home Premium Windows Vista Home Basic Windows Vista Starter

Symptoms

Consider the following scenario:

  • You have a computer that is running Windows Server 2008 R2 Service Pack 1 (SP1) or Windows Server 2008 Service Pack 2 (SP2).

  • The computer works as a Network File System (NFS) server.

  • You create and share files on the NFS server.

  • You use a mount command on a NFS client to connect to the NFS server.

  • You open more than one terminal window on the NFS client.

  • You run the following ls command in each terminal window at the same time to list all shared files:

    cd <NFS share>
    ls –lR

In this scenario, it takes longer than expected to list all the shared files from the NFS server.

Cause

This issue occurs when the NFS client sends a GETATTR call two times in a row. The NFS server has to wait for the ACK packet from the NFS client for the first GETATTR reply packet before it can send the queued second GETATTR reply packet.

Note In most cases, it takes about 0.04 sec to send the second GETATTR reply packet because of delayed ACKs from the NFS client. Therefore, when you execute an ls command, it takes more than two hours to list all files for the attribute information when the total number of files is more than 400,000.
(400,000 * 0.04 sec / 2 Nfs3GetAttr() calls / 3600 sec = 2.22 hours)

You can confirm how long it takes to send the GETATRR reply to the NFS client by monitoring network packets.

Resolution

To resolve this issue, install hotfix 2957486 on the NFS server.

Note Even though this issue has only been observed in Windows Server 2008 R2 or Windows Server 2008, the hotfix also applies to Windows 7 or Windows Vista.

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 this specific problem.

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, submit a request to 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

There are no prerequisites for installing this hotfix.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must 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 7 and Windows Server 2008 R2 file information and 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:

    Version Product Milestone Service branch
    6.1.760 1.18xxx Windows 7 and Windows Server 2008 R2 SP1 GDR
    6.1.760 1.22xxx Windows 7 and Windows Server 2008 R2 SP1 LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 x86-based versions of Windows 7

File name File version File size Date Time Platform
Rpcxdr.mof Not applicable 4,445 10-Jun-2009 21:39 Not applicable
Rpcxdr.sys 6.1.7601.18581 87,552 29-Aug-2014 00:32 x86
Rpcxdr.mof Not applicable 4,445 10-Jun-2009 21:39 Not applicable
Rpcxdr.sys 6.1.7601.22787 87,552 29-Aug-2014 00:33 x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name File version File size Date Time Platform
Rpcxdr.mof Not applicable 4,445 10-Jun-2009 21:00 Not applicable
Rpcxdr.sys 6.1.7601.18581 105,472 29-Aug-2014 00:46 x64
Rpcxdr.mof Not applicable 4,445 10-Jun-2009 21:00 Not applicable
Rpcxdr.sys 6.1.7601.22787 105,472 29-Aug-2014 00:49 x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name File version File size Date Time Platform
Rpcxdr.mof Not applicable 4,445 04-Jul-2013 12:30 Not applicable
Rpcxdr.sys 6.1.7601.18581 262,656 29-Aug-2014 00:20 IA-64
Rpcxdr.mof Not applicable 4,445 09-Jul-2013 06:36 Not applicable
Rpcxdr.sys 6.1.7601.22787 262,656 29-Aug-2014 00:25 IA-64

      

Windows Vista and Windows Server 2008 file information and notes

Important Windows Vista hotfixes and Windows Server 2008 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 Vista/Windows Server 2008" 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:

    Version Product Milestone Service branch
    6.0.600 2.19xxx Windows Vista and Windows Server 2008 SP2 GDR
    6.0.600 2.23xxx Windows Vista and 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" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 x86-based versions of Windows Vista

File name File version File size Date Time Platform
Rpcxdr.mof Not applicable 4,424 18-Sep-2006 21:41 Not applicable
Rpcxdr.sys 6.0.6002.19195 77,312 24-Sep-2014 23:22 x86
Rpcxdr.mof Not applicable 4,424 07-May-2014 23:50 Not applicable
Rpcxdr.sys 6.0.6002.23499 77,824 23-Sep-2014 23:27 x86

For all supported x64-based versions of Windows Vista and of Windows Server 2008

File name File version File size Date Time Platform
Rpcxdr.mof Not applicable 4,424 18-Sep-2006 21:37 Not applicable
Rpcxdr.sys 6.0.6002.19195 90,624 24-Sep-2014 23:32 x64
Rpcxdr.mof Not applicable 4,424 07-May-2014 23:49 Not applicable
Rpcxdr.sys 6.0.6002.23499 91,648 23-Sep-2014 23:52 x64

For all supported IA-64-based versions of Windows Server 2008

File name File version File size Date Time Platform
Rpcxdr.mof Not applicable 4,424 03-Jan-2008 19:03 Not applicable
Rpcxdr.sys 6.0.6002.19195 231,936 24-Sep-2014 23:21 IA-64
Rpcxdr.mof Not applicable 4,424 07-May-2014 23:49 Not applicable
Rpcxdr.sys 6.0.6002.23499 233,984 23-Sep-2014 23:27 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:

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

Information about monitored network packetsTime Delta Description
========== =============================================
0⁠.0000730 NFS:V3 NFSPROC3_GETATTR Service Call Message
0⁠.0000140 NFS:V3 NFSPROC3_GETATTR Service Call Message
0⁠.0000390 NFS:V3 NFSPROC3_GETATTR Service Reply Message
0⁠.0397670 TCP:Flags=...A...., SrcPort=1004, DstPort=NFS(2049)
0⁠.0000200 NFS:V3 NFSPROC3_GETATTR Service Reply Message

Additional file information