Diskeeper 2007 reports \$Extend\$UsnJrnl incorrectly

Diskeeper reported that the \$Extend\$UsnJrnl [Excluded] file size of 872 GB on a 10 GB partition. Diskeeper helpdesk identified problems with OS upgrades regarding \$Extend\$UsnJrnl, however could not address the file size anomaly. Ticket closed. After a little research, I discovered a native command line utility called Fsutil. After executing this utility the problem is resolved.
Note: Do not perform this process on a domain controller.

Screenshots of the original curiosity. Note the extensive, Green – system files.

Defragmentation

Those Green – system files is \$Extend\$UsnJrnl and the File size reported exceeds the actual partition size of 10 GB.

Most fragmented files

Note the Fragmentation percentage is out of range.

journal-1.png

journal-8.png

Resolution Details
From the CMD prompt, Fsutil USN DeleteJournal /D C:

Command shell

When complete, if the Indexing Service was running.
Stop and Start the Indexing Service.
Note that the CI is the Indexing Service. The stop error is a result of the non existent journal. When restarted, the Index rebuilds correctly.

journal-5.png

Now note the far fewer system files in Green.

journal-4.png

The more expected percentage.

journal-3.png

Issue resolved.

1 Comment

  • Diskeeper 2008 reports $Extend$UsnJrnl incorrectly at it.megocollector.com May 13, 2008

    […] I have addressed this anomoly with the same solution that is applicable to Diskeeper 2007 in this article. The process outlined in this article, has been tested and verified to work. […]

Comments are closed.