Jump to content

romanoff

Bug Fixers
  • Posts

    53
  • Joined

  • Last visited

Posts posted by romanoff

  1. Hi,

     

    Defrag when idle option has been moved to 'Task execution conditions' dialog. In order to use it do the following:

    - Check 'Apply additional conditions' in 'Schedule' dialog

    - Click 'Define...' button

    - In 'Idle' group fill 'Start defrag only if the computer is idle for' option.

     

    Hope it helps

     

    Best regards

    Romanoff

  2. Hi,

     

    During the defragmentation Defraggler treats $MFT similarly to normal files but with one exception - it tries to lay it immediately after the first $MFT cluster. This is caused by the fact that the first cluster of $MFT is unmovable.

     

    If Defraggler had increased the number of $MFT fragments during the defrag significantly, please create a debug log from such defrag (http://www.piriform.com/docs/defraggler/troubleshooting/running-defraggler-in-debug-mode) so we can analyze it and solve the issue.

     

    Best regards

    Romanoff

  3. Hi,

     

    these light blue boxes you see with no files inside are used by NTFS internals. There are many different filesystem structures that occupy space on the drive but are completly out of reach for Defraggler - NTFS just does not allow to move or even open them (even in the boot-time defrag). They are not added to the analysis results simply because one cannot do anything with them. Their names are also very confusing for users which are not IT professionals.

     

    As to folders on FAT drives - they also cannot be moved. The filesystem driver does not allow moving first cluster of the directories.

     

    Best regards

    Romanoff

  4. Hi,

     

    Once, Daily, Monthly, Idle etc. are triggers for the defrag, so they determine when Defraggler will be started. In the case of idle trigger, after the defrag is started, Defraggler will not stop/pause when computer activity increases. We may implement such feature in the feature though.

     

    Best regards

    Romanoff

  5. Hi Guys,

     

    When calculating the amount of free space before defrag, Defraggler takes into consideration only the free space which is outside the MFT zone. We would not like to see any files moved into it, as it is the free space reserved by the system for future growth of MFT. It is allocated only if the remaining space (outside the MFT) is used.

    As you can observe on the screenshot attached to the first post, the MFT zone may be pretty large.

     

    Best regards

    Romanoff

  6. Hi,

     

    Every [Folder entry] item in the file list represents a directory index. Such index is simply a data structure containing contents list of a folder. For most directories this fits entirely into the MFT, so no additional space needs to be allocated on the drive. For large folders, on the other hand, the index needs to be moved outside the MFT and therefore it can be fragmented.

     

    Usually it is possible to defragment these indices but in some situations (access or file system restrictions) the operating system does not allow it, what may be the case on your system.

     

    Best regards

    Romanoff

  7. Hi,

     

    About the crash...First of all please try the new version (1.20) as we did several stability fixes there. If the problem is still present, please create a debug log (run Defraggler.exe with /debug option). After the crash occurs in the Defraggler directory there should be also a file named exception.txt. Please attach it along with the log.

     

    Please also note that even if Defraggler crashes it is not possible for it to reboot the system. Problem is probably lying somewhere else in your OS (driver, faulty hardware).

     

    Best regards

    Romanoff

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.