\Documents and Settings\Your Name\Ntuser.dat.log is probably locked and in
use.
Ntuser.dat and Ntuser.dat.log are the HKEY_CURRENT_USER registry hive.
Ntuser.dat is the actual data and Ntuser.dat.log is a backup file.
Ntuser.dat.log is a transaction log of changes to the keys and value entries
in the HKEY_CURRENT_USER hive. Ntuser.dat.log is used to provide fault
tolerance, allowing Windows NT to recover a user profile if a problem occurs
while the NTuser.dat file is being updated.
\Documents and Settings\Your Name\Ntuser.dat.log should only be between 1KB
and 16KB in size. Why worry whether or not it even gets defragmented?
Ntuser.dat.log is more or less continually in use and even if it did get
defragged, it would just fragment right away anyway.
<quote>
What are Ntuser.dat and ntuser.dat.LOG file, anyway, and what are the
differences between them? The Ntuser.dat file contains all the user-specific
configuration settings in the Registry, specifically from the
HKEY_CURRENT_USER subtree, locally. The ntuser.dat.LOG file is a transaction
log. Basically, when the user uses the computer, the user's profile data is
copied to that subkey. As the user makes any changes to the working
environment, the Ntuser.dat file is updated. The ntuser.dat.LOG file is
there to serve as a transaction log, which provides fault tolerance as
updates are made to the Registry database.
<quote>
http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnarexnt01/html/ewn0142.asp
Files Excluded by the Disk Defragmenter Tool
http://support.microsoft.com/kb/227350
It means that everything got defragmented than can be defragmented. Don't
worry, be happy.
If you have enough free space, sometimes running defrag a second or third
may get files that were missed on the first or second run.
Except the files listed below and they are not included in the
defragmentation report...
Files That You Cannot Defragment
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c28621675.mspx
[[After you defragment a volume, you can view the defragmentation report to
see the results. The report includes a list of files that remain fragmented
(having two or more fragments). Some reasons that a file might remain
fragmented include:
* The volume lacks adequate contiguous free space to defragment all files.
Disk Defragmenter requires at least 15 percent free disk space to completely
defragment a volume.
* During defragmentation, a new file is created on the volume in disk space
that was previously free space. In this case, if Disk Defragmenter tries to
move a file to that space to defragment the file, the move fails and the
file remains fragmented.
* The file is the master file table (MFT) on an NTFS volume. Because the
first fragment of the MFT cannot be moved, the MFT is typically contained
within two fragments when sufficient space is available on the volume. If
the MFT is contained within three or more fragments, Disk Defragmenter looks
for free space where the MFT might fit. If sufficient free space exists, the
MFT is moved as a whole (minus the first fragment). If space is not
available, the MFT is not defragmented.
* The file is permanently excluded, in which case it might appear in the
defragmentation report as still being fragmented no matter how many times
you defragment the volume. The following files are permanently excluded from
being defragmented.
* Bootsect.dos
* Safeboot.fs
* Safeboot.csv
* Safeboot.rsv
* Hiberfil.sys
* Memory.dmp
* Paging file ]]
from...
Windows XP Resource Kit: Troubleshooting Disks and File Systems
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c28621675.mspx
Analyze Operation Suggests Defragmenting Disk Multiple Times
http://support.microsoft.com/kb/229850
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In