Well.. is the goal to use iDefrag, and Diskeeper, and vdiskmanager to defrag.. all together in some set order, where maybe even iDefrag is run at the tail-beginning and the tail-end et ...
Or, is vdiskmanger only meant for vdisk's and not for boot camp partitions...
In looking at what Eric posted, this is graphical interface for our command line tools that ONLY work with virtual disks. Boot Camp disks need not apply.
Thanks again to Eric for making a nice tool for Fusion users!
Okay... so does this mean I should just use Diskeeper for the Boot Camp partition, and for the vdisk, use just iDefrag and vdiskmanager GUI and not Diskeeper...
I have Vista in both Boot Camp and also in a vdisk.. which is not preallocated...
As Eric said in the tip in his tools, I believe that the order to do any defragmentation of virtual disks is:
1) Defrag the files inside the guest using the tools supplied by the guest OS or third party tools
2) Then use the VMware Tools or even easier with Eric's graphical tools
3) Defrag the VMDK files using Mac defragmentation tools if necessary
If you are a pre-allocated virtual disk taking the entire space up front, I believe that you just use the guest tools and then Host OS tools if necessary.
If you are using a raw disk (Boot Camp), you should use the defragmentation utilities from Windows or other guest inside the VM.
Hope that helps.
Someone else was advocating defragging the Mac before using diskeeper (or defragging the guest)
You're placing Mac defragging as the last step, but with respect to VMDK files.. and I've only seen idefrag give me the option to defrag the entire disk (not sure what the selection with cursor/grabber really does)
So if I combine the two advocations (yes, advocations), it'd become, for a not-pre-allocated vdisk,
1. Defrag the host
2. Defrag the guest
3. Defrag with Eric's Tool
4. Defrag the host
Preallocating removes the need to use Eric's Tool; and using Boot Camp removes the need to use both Erics's Tool and one of the two stages of Defragging the host (though you'll need to defrag the host irregardless)
Using log file /var/tmp//vmware-markcox/vdiskmanager.log
Failed to defragment: There is not enough space on the file system for the selected operation (14).
Does the above message refer to enough space on the virtual drive, or on the Mac HD...
Using log file
Failed to defragment: There is not enough space on
the file system for the selected operation (14).
Does the above message refer to enough space on the
virtual drive, or on the Mac HD...
Probably the Mac HD - I believe that defragmenting a virtual disk requires as much free space as the maximum space of the virtual disk, unless[/i] it's split into 2GB chunks in which case it only requires 2GB free.