\$Extend\$UsnJrnl [Excess Allocation]

[Pseu]

Hello,

Software: Windows XP Media Center Edition [SP 3].

When I look at the Diskeeper Pro Premier 2008 job report for my “C†drive
[it never appears in the “D†drive report] it shows a defragmented file
called \$Extend\$UsnJrnl [Excess Allocation]; this file increases in size on
a daily basis. I found a so-called fix, which was to type in the run command
box "fsutil usn deletejournal /D C:" without quotation marks, and then
reboot. However, \$Extend\$UsnJrnl [Excess Allocation] begins to grow again
immediately!

If I understand correctly, this problem may have something to do with the
indexing service, even though I have never enabled it.

Any help in preventing this reoccurring problem will be much appreciated.

Regards,

Pseu

 

[MowGreen [MVP]]

A little checking on this issue reveals it's not a new one with Diskeeper -

http://forums.techguy.org/all-other-software/631384-what-c-extend-usnjrnl-j.html
http://it.megocollector.com/?p=381

Read - Posted by: Oliver at October 26, 2007 12:57 AM
http://www.diskeeperblog.com/archives/2007/10/diskeeper_2008_2.html

Wherever the fault lies, DK or MS, the only resolution is to run fsutil,
as you've already posted.
Did you try doing an offline defrag on the reboot with DK after running
fstuil ?

If you changed the Permissions on the root drive, as laid out in this
MSKB: http://support.microsoft.com/kb/311724
you'd best restore the Perms to their previous setting. That's not a
secure setting.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============

 

[Pseu]

Hello,

Despite running "fsutil USN deletejournal /D Câ€, the problem constantly
reoccurs, even though I am not using the indexing service. I believe that the
problem only began when I mistakenly installed Windows Search 4 [which was a
nightmare to uninstall].

I am not sure to how to follow your question "Did you try doing an offline
defrag on the reboot with DK after running fstuil?"

Incidentally, I even uninstalled Diskeeper, rebooted, and then reinstalled
it again, but it made no difference.

There must be a solution to this problem somewhere?

Regards,

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

A little checking on this issue reveals it's not a new one with Diskeeper -

http://forums.techguy.org/all-other-software/631384-what-c-extend-usnjrnl-j.html
http://it.megocollector.com/?p=381

Read - Posted by: Oliver at October 26, 2007 12:57 AM
http://www.diskeeperblog.com/archives/2007/10/diskeeper_2008_2.html

Wherever the fault lies, DK or MS, the only resolution is to run fsutil,
as you've already posted.
Did you try doing an offline defrag on the reboot with DK after running
fstuil ?

If you changed the Permissions on the root drive, as laid out in this
MSKB: http://support.microsoft.com/kb/311724
you'd best restore the Perms to their previous setting. That's not a
secure setting.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============

Hello,

Software: Windows XP Media Center Edition [SP 3].

When I look at the Diskeeper Pro Premier 2008 job report for my “C†drive
[it never appears in the “D†drive report] it shows a defragmented file
called \$Extend\$UsnJrnl [Excess Allocation]; this file increases in size on
a daily basis. I found a so-called fix, which was to type in the run command
box "fsutil usn deletejournal /D C:" without quotation marks, and then
reboot. However, \$Extend\$UsnJrnl [Excess Allocation] begins to grow again
immediately!

If I understand correctly, this problem may have something to do with the
indexing service, even though I have never enabled it.

Any help in preventing this reoccurring problem will be much appreciated.

Regards,

Pseu

 

[MowGreen [MVP]]

From what I've read DK will run a defrag on a reboot prior to the OS
loading. That's an 'offline defrag' or, as DK calls it, Boot Time
Defragmentation.
Are you certain that all files and services associated with DK were
removed when it was uninstalled ? Checking their Support page is not
very helpful as the issues presented have nothing to do with the issue
you cite. Their FAQs page contains info for DK 2007, only:
http://support.diskeeper.com/suppor...Id=1&SId=2&CId=1&Aeid=1&Apid=1&pass=626425787


Don't have much else to offer on this, Pseu. Suggest you contact Diskeeper.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============

Hello,

Despite running "fsutil USN deletejournal /D Câ€, the problem constantly
reoccurs, even though I am not using the indexing service. I believe that the
problem only began when I mistakenly installed Windows Search 4 [which was a
nightmare to uninstall].

I am not sure to how to follow your question "Did you try doing an offline
defrag on the reboot with DK after running fstuil?"

Incidentally, I even uninstalled Diskeeper, rebooted, and then reinstalled
it again, but it made no difference.

There must be a solution to this problem somewhere?

Regards,

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

:

A little checking on this issue reveals it's not a new one with Diskeeper -

http://forums.techguy.org/all-other-software/631384-what-c-extend-usnjrnl-j.html
http://it.megocollector.com/?p=381

Read - Posted by: Oliver at October 26, 2007 12:57 AM
http://www.diskeeperblog.com/archives/2007/10/diskeeper_2008_2.html

Wherever the fault lies, DK or MS, the only resolution is to run fsutil,
as you've already posted.
Did you try doing an offline defrag on the reboot with DK after running
fstuil ?

If you changed the Permissions on the root drive, as laid out in this
MSKB: http://support.microsoft.com/kb/311724
you'd best restore the Perms to their previous setting. That's not a
secure setting.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============



Pseu wrote:

Hello,

Software: Windows XP Media Center Edition [SP 3].

When I look at the Diskeeper Pro Premier 2008 job report for my “C†drive
[it never appears in the “D†drive report] it shows a defragmented file
called \$Extend\$UsnJrnl [Excess Allocation]; this file increases in size on
a daily basis. I found a so-called fix, which was to type in the run command
box "fsutil usn deletejournal /D C:" without quotation marks, and then
reboot. However, \$Extend\$UsnJrnl [Excess Allocation] begins to grow again
immediately!

If I understand correctly, this problem may have something to do with the
indexing service, even though I have never enabled it.

Any help in preventing this reoccurring problem will be much appreciated.

Regards,

Pseu