We believe that for the $BITMAP file the size is being calculated from information in the data stream attribute. The Windows API calls appear to be unaffected by this problem. There are Windows APIs that also retrieve this data but Macrium Reflect reads values directly from the file system meta data. Unlike other imaging products Macrium Reflect uses the file system meta data described above to determine the location and size of key file system structures. Why do other imaging product work correctly if this is a problem with Windows? This caused the file system to update the $BITMAP record incorrectly at the time of installation.įor more information on NTFS, the Master File Table (MFT) and Attributes please see here: This would appear to be a problem with, or an undocumented change to, the NTFS driver shipped with the OS. For the $BITMAP record the $FILE_NAME attribute contains incorrect size information. The $FILE_NAME attribute contains the allocated and actual size of the data in the stream.
Each record has multiple attributes to further describe the record and location and size of data streams. One of these records is named $BITMAP and contains a series of 'Bits' in a data stream that indicate which clusters in the file system are in use and which are not. NTFS contains a series of meta data file records that describe the layout and format of the file system. This will result in an incomplete backup. Note: Do not turn off file system verification to complete the image.
0 kommentar(er)
