JKDefrag Waits On Response From User

[cvhyatt]

We are running jkdefragcmd with the following parameters on our servers:  c:\JkDefragCmd.exe -a 3 -s 10 c: d: e:.  the task is suppose to stop running after 5 hours.

We found a condition where JkDefragCmd.exe was continuing to run.  After logging on as the local admin on the server we found an application popup waiting for us to click on ok.  It also logged the following message in the system event log:

Application popup: JkDefragCmd.exe - Corrupt File : The file or directory C: is corrupt and unreadable. Please run the Chkdsk utility. 

I guess the point here was that JkDefragCmd.exe would not stop running nor could it be killed via pskill until someone responded to this popup.  Is there anyway around this?  I am assuming that if JkDefragCmd finds a disk marked as dirty that it will not run?

Thanks

[jeroen]

The popup is generated by Windows, not by JkDefrag. I will make a note to see if I can check if a disk is dirty before trying to open it. At the moment JkDefrag does not do that because I did not see a need. It does not move files itself, or change the disk in any way. All data moves are done through the Microsoft defragmentation api, so Windows will handle it if something is wrong with the disk. For example if a disk is dirty then Windows will popup a window, as in your case.

[cvhyatt]

Understood.  I guess my main point is that with this running in the background on servers, there is not way to know that pop up has been generated.  In this particualr case, jkdefrag continues to run as a process and waits for someone to hit OK to the popup rather than just exiting after a particular timeout.

[jeroen]

In this particualr case, jkdefrag continues to run as a process and waits for someone to hit OK to the popup rather than just exiting after a particular timeout.

In the current version, yes.

[RJARRRPCGP]

Looks like a hardware problem. Commonly the RAM.