A heavily fragmented file in an NTFS volume may not grow beyond a certain size
A heavily fragmented file in an NTFS volume may not grow beyond a certain size
Introduction
In this scenario, you may experience one of the following issues:
- When you try to copy a file to a new location, you receive the following error message:
In Windows Vista or in later versions of WindowsThe requested operation could not be completed due to a file system limitationIn versions of Windows that are earlier than Windows Vistainsufficient system resources exist to complete the requested service
- When you try to write to a sparse file from the Application log, Microsoft SQL Server may log an event that resembles the following:
In Windows Vista or in later versions of WindowsIn versions of Windows that are earlier than Windows Vista
MORE INFORMATION
We cannot give an exact file size limit for a compressed or a highly fragmented file. An estimate would depend on using certain average sizes to describe the structures. These, in turn, determine how many structures fit in other structures. If the level of fragmentation is high, the limit is reached earlier. When this limit is reached, you receive the following error message:
Windows Vista or later versions of Windows
Versions of Windows that are earlier than Windows Vista
Compressed files are more likely to reach the limit because decompressing and compressing a file increases fragmentation significantly. The limit can be reached when write operations occur to an already compressed chunk location. The limit can also be reached by a sparse file. This size limit is usually between 40 gigabytes (GB) and 80 GB for a very fragmented file.
WORKAROUND
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
Leave a Reply