Article ID: 955547 - Last Review: July 3, 2009 - Revision: 3.0 You cannot create or rename files as expected when you try to use similar file names that differ only in capitalization in an NFS shared directory that was exported from a Windows Server 2003 R2-based NFS Server
On This PageSYMPTOMSYou export a Network File System (NFS) shared directory from an NFS server that is running Windows Server 2003 R2. Then, you mount this NFS shared directory on an NFS client. In this directory, you experience one of the following issues: Issue 1When you try to create files that have the same file names but are capitalized differently, sometimes, only one file is created successfully.Issue 2When you use the mv command to rename a file to the same file name but is capitalized differently, a destination file is generated. However, the source file remains. For example, after you run the mv Test test command, you expect to find that only the file test exists. However, you find that both files, Test and test, exist.CAUSEIn the directory cache buffer, the file names that are the same but that are capitalized differently are stored in case-sensitive order. However, when a method searches the file names, the method makes comparisons that are not case-sensitive. Therefore, when the file names differ only in capitalization, the files cannot be created or renamed as expected. RESOLUTIONHotfix information for Windows Server 2003A 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 Web site: http://support.microsoft.com/contactus/?ws=support
(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.PrerequisitesTo apply this hotfix, you must have the Server of NFS installed on a computer that is running Windows Server 2003 R2.Restart requirementYou must restart the computer after you apply this hotfix.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.For all supported x86-based versions of Windows Server 2003 R2Collapse this table
For all supported x64-based versions of Windows Server 2003 R2Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Article Translations
|
Back to the top
