What happens if my system crashes, someone stops Diskeeper, or my demo expires while Diskeeper is moving a file?
Diskeeper is entirely safe. Refer to the Diskeeper manual for an explanation of what to do in the event of a system crash while Diskeeper is active. Diskeeper defragments files one at a time by making an exact duplicate of the file into a contiguous temporary file. When the copy is complete Diskeeper verifies that the original has not changed since the beginning of the copy procedure; if the file has not changed, Diskeeper raises its priority to 31, opens the original file for exclusive access, performs 2 QIOs to store the map pointers of the original location in the file header of the temporary file and then truncates the temporary file, in effect resetting it for use with the next file. The priority is then lowered to its original level. Because 31 is a real-time priority, the I/O instruction carried with this priority will complete even if any interruption, including a system crash, occurs. If the interruption occurs before Diskeeper raises its priority, Diskeeper simply stops the relocation of the file and the file remains in its current fragments on the disk. The worst thing that can happen is that some blocks may remain allocated to the Diskeeper temporary file. You can run the DISK_VALIDATE procedure within Diskeeper's directory, or wait until you restart Diskeeper at which time the temporary file will automatically be deleted. If a Diskeeper demo expires while Diskeeper is in the middle of a pass, the pass will still complete.
If this FAQ helped, please let us know. If you didn't find the answer to your question here please e-mail
|
