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. "ERROR_FILE_SYSTEM_LIMITATION" when a write operation is performed on a very large file in Windows Server 2012 or Windows Server 2012 R2

"ERROR_FILE_SYSTEM_LIMITATION" when a write operation is performed on a very large file in Windows Server 2012 or Windows Server 2012 R2

View products that this article applies to.

Symptoms

When a write operation is performed on a very large file (more than 100 gigabytes [GB]) that is stored on a data-deduplication-enabled volume in Windows Server 2012 or Windows Server 2012 R2, the write operation fails. Additionally, you receive the following error message:

ERROR_FILE_SYSTEM_LIMITATION

Note When the issue occurs, the file goes into a maximum fragmentation state, and no data deduplication mechanism can repair the file. 

↑ Back to the top

Cause

This problem occurs because the NT file system (NTFS) reached the maximum number of extents. When the limit is reached, NTFS returns the ERROR_FILE_SYSTEM_LIMITATION error message. 

↑ Back to the top

Resolution

To resolve the problem, follow these steps:

  1. Run Defrag on the volume on which this problem occurs. For more information, see Defrag.
  2. If the problem is not solved, run the deduplication optimization job. For more information, see Install and Configure Data Deduplication.
  3. If the problem continues to occur, follow these steps:
    1. Copy the file to a new file.
    2. Delete the original file.
    3. Rename the new file by using the original file name.
    4. Optimize the new file.

↑ Back to the top

More Information

Some best practices for data deduplication: 
  • If you plan to use very large files (more than 500 GB) that have many in-place chunks, you should format the volume by using the "/L" option to accommodate large-size file records. By default, the volume is formatted to use small-size file records. 
  • After data deduplication is performed on a volume for the first time, you should perform a full backup immediately afterward.
  • Perform garbage-collection jobs weekly on the chunk store to remove chunks that are no longer used. 
  • After a garbage-collection job is finished, you should perform a full backup on the volume. You should do this because the garbage-collection job may result in many changes in the chunk store if many files were deleted after the last garbage-collection job. 

↑ Back to the top

Keywords: kbexpertiseadvanced, kbtshoot, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2891967
Revision : 1
Created on : 1/7/2017
Published on : 10/18/2013
Exists online : False
Views : 481