Client Data is Corrupted When Written to an NTFS Server

 Last reviewed: March 13, 1995
Article ID: Q125904
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

Files created on an NTFS server volume by a network client may contain zeros (NULs) in place of the data the client software intended to write. The client software may not immediately detect that the data has been corrupted if the client is using caching. Looking at the file from the server or from another client will show that the file contains zeros.

This problem occurs very infrequently and requires extensive file creation to reproduce. Only one corrupted file was encountered in one a test machine when 30,000 files were created during heavy disk activity.

WORKAROUND

To work around this problem, use a File Allocation Table (FAT) or a High Performance File System (HPFS) partition.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbnetwork kbbug3.50
KBSubcategory: ntfilesys
Additional reference words: 3.50 prodnt

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 13, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.