What is C:\$Extend\$UsnJrnl:$J:$DATA

  • Thread starter Thread starter _Who
  • Start date Start date
W

_Who

60 C:\$Extend\$UsnJrnl:$J:$DATA
1 C:\$LogFile
1 C:\$Bitmap
1 C:\$Boot
1 C:\$MFTMirr
1 C:\$MFT::$BITMAP


Should I be concerned that C:\$Extend\$UsnJrnl:$J:$DATA has 60 fragments?
And that the others have 1?

If so, how can I defrag them.


Thanks
 
_Who said:
60 C:\$Extend\$UsnJrnl:$J:$DATA
1 C:\$LogFile
1 C:\$Bitmap
1 C:\$Boot
1 C:\$MFTMirr
1 C:\$MFT::$BITMAP


Should I be concerned that C:\$Extend\$UsnJrnl:$J:$DATA has 60 fragments?
And that the others have 1?

If so, how can I defrag them.


Thanks
Click to expand...
I would be much more concerned about knowing which program created these
folders. I would also wonder what purpose the contents of the folders
serve. There are problably lots of other things about them which are cause
for concern. The last of these things is whether they need defragmentation
or not.
Jim
 
I assumed they were system files.
When I show the folder C:/ they don't show.
Got any suggestions?

thanks
 
Jim said:
I would be much more concerned about knowing which program created these
folders. I would also wonder what purpose the contents of the folders
serve. There are problably lots of other things about them which are cause
for concern. The last of these things is whether they need defragmentation
or not.
Click to expand...

They're part of the NTFS structure, the $USN Journal is not read or used
by Windows but the others are essential to the health and proper
operation of the NTFS file system.

John
 
John John (MVP) said:
They're part of the NTFS structure, the $USN Journal is not read or used
by Windows but the others are essential to the health and proper operation
of the NTFS file system.

John
Click to expand...

So it would appear that the fact that $USN Journal is fragmented is not
important.
The others each have one fragment. Is that worrisome?
thanks
 
_Who said:
So it would appear that the fact that $USN Journal is fragmented is not
important.
The others each have one fragment. Is that worrisome?
thanks
Click to expand...

I wouldn't bother too much with it. Windows doesn't use this but other
applications use it to keep track of file changes, by default this is
disabled on Windows XP installations but any application can turn it on
if it needs it.

Change Journals
http://msdn.microsoft.com/en-us/library/aa363798.aspx

On Windows 2000 this journal was enabled by default and the file system
driver (ntfs.sys) could not overcome corruption in this file, although
infrequent, damage to this file had a pesky little side effect of
rendering the disk unreadable and unmountable. Changes were made to the
Windows XP file system driver and errors in the journal are ignored by
the driver and the disk can be mounted and read even when the journal is
corrupted.

Creating, Modifying, and Deleting a Change Journal
http://msdn.microsoft.com/en-us/library/aa363877(VS.85).aspx

Fsutil usn
http://technet.microsoft.com/en-us/library/cc788042.aspx

Change Journal Records
http://msdn.microsoft.com/en-us/library/aa363803(VS.85).aspx

Keeping an Eye on Your NTFS Drives: the Windows 2000 Change Journal
Explained
http://www.microsoft.com/msj/0999/journal/journal.aspx

John
 
John John (MVP) said:
I wouldn't bother too much with it. Windows doesn't use this but other
applications use it to keep track of file changes, by default this is
disabled on Windows XP installations but any application can turn it on if
it needs it.

Change Journals
http://msdn.microsoft.com/en-us/library/aa363798.aspx

On Windows 2000 this journal was enabled by default and the file system
driver (ntfs.sys) could not overcome corruption in this file, although
infrequent, damage to this file had a pesky little side effect of
rendering the disk unreadable and unmountable. Changes were made to the
Windows XP file system driver and errors in the journal are ignored by the
driver and the disk can be mounted and read even when the journal is
corrupted.

Creating, Modifying, and Deleting a Change Journal
http://msdn.microsoft.com/en-us/library/aa363877(VS.85).aspx

Fsutil usn
http://technet.microsoft.com/en-us/library/cc788042.aspx

Change Journal Records
http://msdn.microsoft.com/en-us/library/aa363803(VS.85).aspx

Keeping an Eye on Your NTFS Drives: the Windows 2000 Change Journal
Explained
http://www.microsoft.com/msj/0999/journal/journal.aspx

John
Click to expand...

Thanks for the sites.
 
John John (MVP) said:
I wouldn't bother too much with it. Windows doesn't use this but other
applications use it to keep track of file changes, by default this is
disabled on Windows XP installations but any application can turn it on if
it needs it.

Change Journals
http://msdn.microsoft.com/en-us/library/aa363798.aspx

On Windows 2000 this journal was enabled by default and the file system
driver (ntfs.sys) could not overcome corruption in this file, although
infrequent, damage to this file had a pesky little side effect of
rendering the disk unreadable and unmountable. Changes were made to the
Windows XP file system driver and errors in the journal are ignored by the
driver and the disk can be mounted and read even when the journal is
corrupted.

Creating, Modifying, and Deleting a Change Journal
http://msdn.microsoft.com/en-us/library/aa363877(VS.85).aspx

Fsutil usn
http://technet.microsoft.com/en-us/library/cc788042.aspx

Change Journal Records
http://msdn.microsoft.com/en-us/library/aa363803(VS.85).aspx

Keeping an Eye on Your NTFS Drives: the Windows 2000 Change Journal
Explained
http://www.microsoft.com/msj/0999/journal/journal.aspx

John
Click to expand...

Guess there are hidden and REALY HIDDEN files'
The following produces some names but not the ones we've discussed.

dir /s/a:h C:\*$*
 
Back
Top