Weird ? $Extend message

[UlfZi]

In log I have:
         19    13.851.577.808       2.352  C:\$Extend\$UsnJrnl:$J:$DATA

I'm wondering, that a 13 GB file only uses 2.352 clusters ?

My Problem:
After increasing an NTFS partition from ~50 to ~60GB, the new free area remains dark blue (reserved by NTFS), after MyDefragGUI 2.1.2 + 4.1.2 run, so I stay on plenty unmovable files.

- Why is there no option from MyDefragGui to sort files by path inside zones like monthly opto from normal MD?
- If using sort by path from MyDefragGui, does it sort inside the zones, or resort the whole disk ?

[BloodySword]

The USN-Journal is a sparse file. http://en.wikipedia.org/wiki/Sparse_file
See How do I defragment "C:\$Extend\$UsnJrnl:$J:$DATA"?
Since Windows 7 it can be defragmented and moved like any other normal file on the system.

I can not answer the rest of your questions since I don't use MyDefragGUI.
MyDefrag comes with a built in Script/Drive chooser.

Please upgrate to the latest MyDefrag version wich fixes most bugs.

[Darlis]

- Why is there no option from MyDefragGui to sort files by path inside zones like monthly opto from normal MD?

You have to ask the author. This forum is about MyDefrag.

- If using sort by path from MyDefragGui, does it sort inside the zones, or resort the whole disk ?

The sort by options are only using one zone.

[UlfZi]

Thanks,
... but MyDefragGUI links exactly to this forum.

You have to ask the author. This forum is about MyDefrag.

- If using sort by path from MyDefragGui, does it sort inside the zones, or resort the whole disk ?

The sort by options are only using one zone.

And witch one of the existing 5 ?

[Darlis]

- If using sort by path from MyDefragGui, does it sort inside the zones, or resort the whole disk ?

The sort by options are only using one zone.

And witch one of the existing 5 ?

I just tested the first two but I guess they all have only one zone.

[UlfZi]

The USN-Journal is a sparse file. http://en.wikipedia.org/wiki/Sparse_file
See How do I defragment "C:\$Extend\$UsnJrnl:$J:$DATA"?

I have run fsutil usn deletejournal /n c:

But again the "free" area is occupied by the journal file.
Maybe I should use:
     fsutil usn deletejournal /D c:

[BloodySword]

Yes. /n will only notfy a delete to other programs who are use it. /D will delete the journal and if a program want to use it again, it will be recreated.

[jeroen]

Yes. /n will only notfy a delete to other programs who are use it. /D will delete the journal and if a program want to use it again, it will be recreated.

That is not what the Microsoft documentation on the fsutil command says, see Fsutil usn

[Darlis]

Thats strange. The german manpage for deletejournal says this:

C:\Windows\system32>fsutil usn deletejournal /?
Syntax : fsutil usn deletejournal <Flags> <Volpfad>
<Flags>
  /D : Löschen     delete
  /N : Benachrichtigen     notify
  Beispiel : usn deletejournal /D C:

Must be a wrong translation, since /n does delete the journal like it's described on the TechNet page.

[BloodySword]

For logic reason it is obious that /D stands for DELETE and /n stands for notify. Seems like someone wrote it to the wong line in the manpage.

[UlfZi]

After using fsutil usn deletejournal /n c: the "free" area at the end of my disk was still marked as reserved after new MyDefrag analyse run, so MyDefrag couldn't use that area for optimizing.

The only thing which helped was to insert the deleteJournal() command in the monthly script.

[BloodySword]

Note that the DeleteJournal() command is not executet BEFORE analyzing yet. That means the occupied blocks of the Jorunal are still there and MyDefrag will not move a file to this locations. You have to cancel the script and restart it, then the blocks are free.

[jeroen]

After increasing an NTFS partition from ~50 to ~60GB, the new free area remains dark blue (reserved by NTFS)

What exactly do you mean by "reserved by NTFS"? Do you mean the "NTFS reserved area"? In that case see the MyDefrag PlaceNtfsSystemFiles command. You will want to reboot after running MyDefrag, or you can use the MyDefrag DismountVolume command.

After using fsutil usn deletejournal /n c: the "free" area at the end of my disk was still marked as reserved after new MyDefrag analyse run, so MyDefrag couldn't use that area for optimizing.

The USN journal (C:\$Extend\$UsnJrnl:$J:$DATA) is a sparse file. A sparse file is a file that has been declared as a big file (in your case 13GB) but does not actually use all that space. In your case it uses only 2.352 clusters. So, the dark blue area is not the USN journal. When you delete the USN journal with the fsutil command then the clusters will go down and the gigabytes will stay the same.

[UlfZi]

After increasing an NTFS partition from ~50 to ~60GB, the new free area remains dark blue (reserved by NTFS)

What exactly do you mean by "reserved by NTFS"? Do you mean the "NTFS reserved area"?

I'm not sure exactly. Hovering the mouse over that area stated something with "reserved" and "NTFS". Sorry, Now it's difficult to reproduce.

In that case see the MyDefrag PlaceNtfsSystemFiles command. You will want to reboot after running MyDefrag, or you can use the MyDefrag DismountVolume command.

Much thanks for this additional hints. Hopefully next time I remember it.

After using fsutil usn deletejournal /n c: the "free" area at the end of my disk was still marked as reserved after new MyDefrag analyse run, so MyDefrag couldn't use that area for optimizing.

The USN journal (C:\$Extend\$UsnJrnl:$J:$DATA) is a sparse file. A sparse file is a file that has been declared as a big file (in your case 13GB) but does not actually use all that space. In your case it uses only 2.352 clusters. So, the dark blue area is not the USN journal. When you delete the USN journal with the fsutil command then the clusters will go down and the gigabytes will stay the same.
[/quote]
Thanks for your explanation. That might have confused me. My assumption was, the area was occupied by the USN journal, because of the roundabout same size.