Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-8480

Only zero-fill newly allocated files for Windows versions that are affected by NTFS issue

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.4.0-rc0
    • Fix Version/s: 2.4.10, 2.5.5
    • Component/s: Storage
    • Labels:
    • Environment:
      Windows Server 2008 R2 / Windows 7
    • Backwards Compatibility:
      Fully Compatible

      Description

      Issue Status as of March 30, 2014

      ISSUE SUMMARY
      On Windows platforms code was previously added to zero-fill each newly allocated data file in order to work around an issue described in this Windows Knowledge Base article. As this issue only applies to Windows 7 and Windows Server 2008 R2, the zero-filling unnecessarily slows down file allocation on other, unaffected Windows versions, namely Windows 8 and Windows Server 2012.

      USER IMPACT
      Slower file allocation on Windows platforms.

      SOLUTION
      The fix is to restrict the zero-filling of newly allocated files to only the affected Windows versions.

      WORKAROUNDS
      None

      AFFECTED VERSIONS
      All recent production release versions up to 2.4.9 are affected.

      PATCHES
      The fix is included in the 2.4.10 production release and the 2.5.5 development version, which will evolve into the 2.6.0 production release.

      Original Description

      Currently due to an NTFS issue the server writes zeros to the data file when allocating it. This is not necessary if the OS has the http://support.microsoft.com/kb/2731284 hotfix.
      The server needs to detect the install of the above hotfix and bypass writing of 0's

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: