Common Cause of "Error performing inpage operation" Explained

Last reviewed: April 10, 1997
Article ID: Q141117
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51

SUMMARY

When copying files from a diskette on a Windows NT computer, you may occasionally experience an "Error performing inpage operation".

In this scenario, this error usually indicates physical problems on the diskette media, and is probably unrelated to paging operations involving the Windows NT paging file, despite the wording of the error message.

MORE INFORMATION

Copy utilities commonly use the CopyFile() Win32 API to copy files.

For small files (where small is arbitrarily defined in the Windows NT source code as less than 256 kilobytes) the Windows NT CopyFile() API does not actually open the source file and read from it using the CreateFile() and ReadFile() APIs as might be expected.

Instead, the CopyFile() API creates a File Mapping and maps the file into virtual memory. Data is then read from the file by simply accessing this memory. As the memory is accessed, the required portions of the file are paged into memory on demand. This leverages the paging functionality of the Windows NT Virtual Memory Manager, but introduces the jargon of Paging into this particular file copy scenario.

Consequently, if I/O errors occur while processing a CopyFile() API for a "small" file, they will not be reported as File I/O Errors. Instead, as these errors are detected in what is effectively a paging operation (albeit unrelated to the Windows NT paging file), they will be reported as "Error performing inpage operation".

Additionally, errors caused by network connectivity can cause these errors. Mismatched MTU sizes or truncation of a packet at a router can result in this error when files larger than the largest packet size are copied over the network. In essence, the network connection is the media that has the physical problem.

REFERENCES

For more information on memory-mapped files, refer to the following:

  • Helen Custer's "Inside Windows NT", Section 6.2.1, "Sharing Memory".
  • The Win32 Programmer's Reference, Volume 2, Chapter 47, "File Mapping".


Additional query words: prodnt copy scopy xcopy robocopy winfile file
manager
Keywords : kbnetwork ntutil
Version : 3.1 3.11 3.5 3.51
Platform : WinNT


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: April 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.